Technical SEO Audit: From URL Inventory to Verified Fixes

Collect URLs from the sitemap, internal navigation and Search Console. Keep historical URLs separate from current published pages. Record HTTP status, final destination, canonical URL, robots directives, title and the page’s purpose. A Search Console exclusion total alone does not tell you how many current pages are broken.

Classify each URL as intended for search, intentionally excluded, redirected, removed or requiring investigation. For an ecommerce site, an account page may be intentionally excluded while a product page is intended for indexing. Treat these cases differently instead of trying to eliminate every exclusion.

Open a known missing URL and confirm the actual HTTP response. A friendly error page returned with status 200 can confuse the inventory. Follow redirects to their final destination and check that the destination matches the original user’s likely task.

Compare the canonical and sitemap URL with the destination. Look for unnecessary chains, inconsistent hosts and references to removed pages. Test both a normal visitor request and the rendered page; do not infer crawler access from a screenshot alone.

Can a visitor reach the important page through meaningful internal links? Does its main content explain something useful beyond a different city or keyword? Record the unique purpose in one sentence. If several pages have the same purpose, evaluate consolidation and an appropriate redirect rather than adding more keyword variants.

For JavaScript-heavy pages, inspect the rendered content and links. Compare what the initial response provides with what appears after rendering. Keep key navigation as real links and ensure the content is available without a user needing to trigger an unrelated interaction.

List the schema types emitted by the template and compare their claims with visible content. Check entity identifiers, authors, dates and images. Use Google’s relevant structured-data documentation to determine eligibility; syntactically valid JSON does not automatically qualify for a rich result.

For reviews, distinguish displaying client feedback from eligibility for Google review snippets. Do not invent a Product entity for a service business merely to obtain stars. Remove misleading markup while keeping authentic feedback visible.

For each issue record the affected URLs, expected behavior, observed behavior, cause hypothesis, proposed change and post-release check. Prioritize access failures and misleading signals before cosmetic metadata adjustments. Keep each fix reversible.

After deployment, repeat the relevant requests and inspect the live HTML. Submit an updated sitemap when appropriate, then monitor crawl and indexing changes over time. A fixed technical issue does not guarantee ranking gains; content relevance, competition and other signals still matter.