Skip to content

GBP audit template

Record what the profile says, where the data came from, and what you decided.

Capture what the profile and connected provider reported on a known date. Do not treat a provider score as a guarantee from Google, and give every recommendation a source and an owner.

Request access Explore the platform
LOC 3581294627
Points
9
Range
2–12
Source
Demo
Synthetic points show why local visibility should be read as a spatial pattern, not a guaranteed customer rank.

What to look for

Get the answer without losing sight of where it came from.

01

Record the profile facts

Business identity, verification, categories, details, hours, attributes, services, photos, posts, and website.

02

Add performance context

Search visibility, competitor observations, reviews, customer actions, reporting window, and data provider.

03

Turn findings into a plan

Separate factual corrections, optimization ideas, content needs, risks, owners, approvals, and follow-up.

Made for real work

Start here, then shape it around the site in front of you.

The examples give you a useful structure. Replace them with the pages, people, findings, and decisions that belong to the project.

GBP audit template / What to include

  1. 01
    Record the profile facts

    Business identity, verification, categories, details, hours, attributes, services, photos, posts, and website.

  2. 02
    Add performance context

    Search visibility, competitor observations, reviews, customer actions, reporting window, and data provider.

  3. 03
    Turn findings into a plan

    Separate factual corrections, optimization ideas, content needs, risks, owners, approvals, and follow-up.

From finding to follow-up

See where the work stands—and what still needs to happen.

  1. 01Found

    Netrix records the page and the issue it found.

  2. 02Reviewed

    Someone checks the finding in context.

  3. 03Approved

    The right person chooses what should change.

  4. 04Applied

    A supported connection accepts the change.

  5. 05Checked

    Netrix reads the public page again.

  6. 06Shared

    The report summarizes the audit and fixes currently marked applied.

A few things worth knowing

Netrix can prepare the work. Your team still makes the call.

  1. 01
    Nothing publishes itself

    AI drafts and supported SEO changes wait for an authorized person to act.

  2. 02
    A write is not proof

    Netrix records when a provider accepts a change, then checks the public page separately. If it cannot read the page, the result stays unknown.

  3. 03
    Limits belong in the open

    When a feature depends on another provider or stops short of a complete workflow, the page should say so.

Keep exploring

More on this part of the work

Browse all resources

Audit template

Start with what you will measure. End with what you checked after the fix.

Use a technical SEO audit checklist covering scope, crawl quality, indexing, metadata, architecture, performance, QA, and reporting.

Reporting template

Explain the audit clearly without turning the whole site into one score.

Structure a client-ready technical SEO report with scope, method, findings, priorities, page examples, remediation, and limitations.

Remediation template

Turn the recommendation into a change someone can own and test.

Plan technical SEO remediation with page details, priorities, exact targets, owners, approvals, dependencies, QA, and recovery.

See how it fits your team

Bring the crawl, the review, and the follow-up together.

Request access