Run a website audit and verify the correction

1. Enter the public URL

Open Website SEO audit, paste the URL you want reviewed and select Run audit. Use a public page rather than an editor preview or a signed-in dashboard. No Google, CMS or GitHub connection is needed for this first inspection.

For a specific complaint, keep the exact URL in your notes. A homepage audit alone is not enough to investigate a broken link inside a particular article.

2. Check what was actually scanned

Read Pages scanned, Links checked and Audited before looking at the total score. The report covers pages it could discover and read. Failed reads and a truncated crawl leave gaps; a missing result is not a passing check.

If the report says a page lacks a heading or body text, open that page in a browser. Some sites build their content with JavaScript after the initial HTML loads. Determine which version supplied the audit evidence before replacing content that is already visible to readers.

3. Open the finding and choose one correction

Under a finding, read Affected pages, Evidence and How to fix. Confirm that the affected URL is the intended page and that the cited issue still exists.

For example, if a navigation link leads to an old pricing address, inspect the current pricing page before choosing a replacement. Rewriting the link label without changing its destination would leave the problem intact.

Handle a small, related set of issues together. A repeated title may come from a shared template; changing every article individually would miss the source of the duplication.

4. Generate and review the fix

Select Generate fix. Read the proposed change alongside the existing page. If the interface says a baseline template was generated because AI was unavailable, treat it as a starting template, not as a tailored repair.

For a copy change, you can continue with a specific request:

For this page, show the original title and proposed title. Rewrite the opening for a buyer comparing options. Preserve supported product capabilities. Identify any claim that needs my confirmation, and leave the rest ready to review.

A suggested description should accurately summarize the page that exists. If it promises a comparison table or downloadable report, check that the page actually includes one.

5. Apply through the correct publishing workflow

For a website repository, select Fix through GitHub and follow the repository connection steps. Check the intended repository, changed files and preview. For a WordPress article, use the connected site’s draft and publishing workflow.

Confirm the change was published before declaring the issue fixed. A draft, a proposed patch and a live page are separate states.

6. Recheck the URL, then measure separately

Open the published URL, follow the repaired link or inspect the changed content, then repeat the relevant audit check. Keep the exact URL, change and publication date in the result. An inaccessible or unscanned page remains outside the verified scope.

For performance, use Search Console to compare the same page and query scope over consistent periods. The completed output here is an inspected correction, not a promise of traffic or AI citations.