Technical SEO, on-page optimisation, local search, authority building and visibility in AI-assisted search.
View topic guides01 / GUIDE
A technical SEO audit should answer one question: what is stopping the right pages from being discovered, understood and trusted?
A good audit is not a 200-item export where every warning has equal importance. It identifies what can materially affect crawling, indexing, relevance, user experience or measurement, then prioritises the work by impact and risk.
Technical SEO is strongest when crawl data, Search Console evidence, rendered pages, server behaviour and business intent are reviewed together.
02 / GUIDE
1. Crawlability and status codes
Start with every important indexable URL and verify its HTTP response. Look for unintended 3xx chains, 4xx errors, soft 404s, 5xx failures, blocked resources and inconsistent protocol or hostname behaviour.
Then identify URLs search engines can discover that should not exist as indexable pages: search results, parameter duplicates, empty archives, test pages, staging copies and low-value generated URLs.
03 / GUIDE
2. Indexability, robots and canonicalisation
For each important URL, verify robots directives, canonical tags and sitemap inclusion tell the same story. A page should not normally be in the sitemap while also declaring noindex. Canonicals should identify the preferred version rather than point casually to a different page.
Use Search Console URL Inspection for key pages because a crawler only shows what the website currently says. Search Console can show how Google last processed the URL.
04 / GUIDE
3. XML sitemaps
A sitemap should contain canonical URLs that you actually want indexed. Remove dead, redirected, duplicate, noindex and utility URLs. Keep last-modified data accurate if it is emitted. Submit the sitemap to Search Console and monitor whether important URLs are being discovered and indexed.
05 / GUIDE
4. Internal linking and crawl depth
Important pages should be reachable through normal HTML links from relevant parts of the site. Look for orphan pages, excessive click depth, vague repeated anchors and commercial pages that receive little internal authority.
Internal linking is both navigation and information architecture. Descriptive anchors help people and search engines understand the relationship between pages.
06 / GUIDE
5. Titles, headings and search intent
Technical SEO does not stop at status codes. Check for duplicated or missing titles, unclear H1s and pages competing for the same intent. If two URLs are trying to rank for the same commercial query, adding more keywords to both rarely solves the architecture problem.
07 / GUIDE
6. Rendering, JavaScript and mobile behaviour
Verify that primary content and links are available to search engines after rendering. Check mobile navigation, accordions, lazy-loaded content, client-side routing and JavaScript errors. Modern JavaScript sites can rank well, but important content should not depend on fragile execution paths when a simpler implementation is available.
08 / GUIDE
7. Core Web Vitals and real performance
Review both lab diagnostics and field data where available. Core Web Vitals focus on loading, responsiveness and visual stability, but a single Lighthouse score is not the same thing as real-user performance. Diagnose the actual bottleneck: server response, render-blocking work, oversized images, JavaScript execution, layout shifts, fonts or third-party scripts.
Performance work should improve user experience without destabilising a site that is already healthy.
09 / GUIDE
8. Structured data
Validate structured data against the visible page. Use the most specific type that is genuinely supported and remove stale or invented claims. Structured data helps machines interpret entities and page relationships; it should not be used to describe things users cannot see or verify.
10 / GUIDE
9. Measurement and evidence
An audit should end with a measurable baseline: indexed pages, non-indexed reasons, organic landing pages, major query clusters, Core Web Vitals, crawl errors and conversions. Without measurement, teams can fix dozens of minor warnings while missing the pages actually losing revenue.
11 / GUIDE
A useful audit priority model
- P0: deindexing, outages, blocking directives, broken migrations, widespread 5xx/4xx or canonical disasters.
- P1: high-value pages not indexed, severe intent conflicts, broken internal architecture, major mobile/rendering failures.
- P2: performance, metadata, structured data, internal-link and content improvements with clear opportunity.
- P3: cosmetic warnings or theoretical issues with little evidence of impact.
Prioritisation is what turns an audit into a recovery or growth plan.
12 / GUIDE
Primary Google references
Google’s SEO Starter Guide, crawling/indexing documentation and Search Console are the primary references for Google-specific technical behaviour. PluginPip uses third-party tools to collect evidence, not to overrule the search engine’s own documentation.