How to Audit On-Page SEO: A Practical Checklist

Set the page goal and baseline

Record the audience, target task, query theme, canonical URL, conversion action, and business priority. Identify other site URLs that may satisfy the same intent.

Capture impressions, clicks, position, entrances, engagement, and conversions before editing so the outcome can be measured.

Check crawlability and HTTP behavior

Confirm the canonical URL returns 200, uses HTTPS, follows a deliberate redirect path, and is not blocked. Test without a browser session so personalization does not hide a problem.

Review Google's robots.txt guidance and verify CDN behavior for crawlers.

Verify indexability and canonical signals

Inspect meta robots, X-Robots-Tag, canonical, sitemap inclusion, and internal links. The canonical should normally be absolute, indexable, and successful.

Use Search Console URL Inspection for Google's observed state, not only browser HTML.

Review title, description, and headings

The title must identify the page job and distinguish it from neighboring URLs. The description should accurately preview the result. Use one H1 and descriptive H2 and H3 headings.

Answer the main question early and avoid repeating keywords for density. Search intent and useful coverage matter more.

Audit content evidence and links

Check accuracy, originality, freshness, examples, and primary-source support. Add information gain through tested workflows, data, screenshots, decisions, and failure cases.

Use contextual internal anchors and repair broken destinations. Classify links with the Link Extractor.

Check media, schema, and priorities

Compress images, specify dimensions, write accurate alt text, and verify Open Graph with the Meta Tag Checker. Validate truthful JSON-LD with the Schema Checker.

Fix noindex, canonical, server, and access defects before cosmetic warnings. Annotate release dates and monitor search and conversion outcomes.

Turn findings into a prioritized remediation plan

Classify each finding by evidence, consequence, effort, ownership, and confidence. A blocked or non-indexable canonical page is a release blocker. A duplicated title across important pages is usually high priority. A stylistic description improvement is useful but should not delay access and indexing fixes.

1. Fix server, redirect, robots, noindex, and canonical conflicts.
2. Resolve intent overlap and weak page purpose.
3. Improve titles, headings, answer coverage, evidence, and links.
4. Correct media, structured data, and presentation defects.
5. Measure the outcome against the recorded baseline.

Do not export a long list of warnings without explaining which defect should be addressed first and why.

Verify fixes on the production URL

After release, fetch the final public URL without a logged-in session. Confirm the status, selected canonical, robots directives, rendered body, title, H1, internal links, image dimensions, and JSON-LD match the intended page. Then inspect the URL in Google Search Console and confirm the XML sitemap contains the canonical address.

Annotate the deployment date and monitor impressions, queries, clicks, click-through rate, engagement, and conversions. If impressions rise but clicks do not, review the title and snippet. If irrelevant queries appear, clarify the page job. If visibility remains absent, investigate indexing, internal links, intent, content value, and authority before adding more keywords.

Common failure patterns and how to diagnose them

Start with the earliest failing layer. If a request does not return the expected page, inspect DNS, redirects, HTTP status, content type, firewall behavior, and access controls before changing extraction or metadata rules. If the correct document arrives but the result is empty, compare initial HTML with the rendered page and determine whether JavaScript supplies the missing information.

When only some fields are wrong, inspect the page source and identify which signal produced each value. A stale canonical, duplicated title, malformed JSON-LD block, relative URL, or CMS fallback should be corrected at its source. Avoid adding a special case for one URL when the same template defect affects a wider section of the site.

Finally, distinguish a deterministic failure from a recommendation. Invalid JSON, an unreachable URL, or a conflicting index directive can be proven. Content usefulness, ideal wording, and business priority still require human judgment. A professional report should show the evidence, explain the consequence, and avoid presenting a heuristic as a universal rule.

Production quality checklist

Validate the exact production URL, not only a CMS preview, local fixture, or isolated code sample. Confirm the requested URL, final URL, HTTP status, content type, and visible result agree with the page you intended to process. Test at least one normal case, one sparse page, one redirected URL, and one expected failure so the interface communicates limitations clearly.

• Keep source URLs and observation times with exported results.
• Use descriptive labels, headings, and error messages.
• Specify image dimensions and keep media files lightweight.
• Test keyboard access and narrow mobile layouts.
• Separate automatic checks from recommendations requiring judgment.
• Respect access controls, publisher policies, privacy, and applicable law.

After deployment, rerun the workflow against representative URLs and monitor for changes in output size, missing fields, status codes, response time, and template behavior. Keep a known-good result for comparison. When a check fails, fix the source template or data pipeline rather than hiding the warning in the interface.