Digital AuditsModule 2: Website and search reviewLesson 5 of 12
Course progress33%
22 min lesson · Updated August 2026
How do you audit technical and on-page SEO?
A technical and on-page SEO audit checks whether search systems can discover, fetch, render, understand and index the intended pages, and whether those pages clearly satisfy real search needs without contradictory controls.
What you will learn
By the end, you will understand:
Trace a URL from discovery through indexing and presentation
Audit status, robots, canonical, sitemap, rendering and internal-link controls
Review page titles, headings, content and structured data in context
Visual explainer
See the idea clearly.
123
Priority URLs move through discovery, robots access, server response, rendering, canonical selection, indexing and search presentation; conflicting controls are highlighted at each gate.
Start with intended URL states
State
Meaning
Indexable canonical
The preferred useful page should be discoverable, fetchable and eligible for indexing.
Duplicate/alternate
Consolidate to a preferred URL using suitable redirect/canonical and consistent links.
Private/non-search
Use authentication or noindex as appropriate; robots.txt alone does not remove an indexed URL.
Removed
Return an accurate 404/410 or redirect only when a relevant replacement exists.
Follow the technical pipeline
01
Inventory important URLs
02
Check internal discovery/sitemap
03
Fetch robots rules
04
Inspect HTTP status/redirect chain
05
Render key content and links
06
Check robots meta/header
07
Review canonical signals
08
Inspect index evidence
09
Validate search appearance
10
Reconcile with intended state
Controls can conflict
A URL may be in the sitemap but redirect elsewhere, declare a different canonical, be blocked from crawling or carry noindex. Search engines interpret signals rather than obeying a single magic setting.
Do not block crawling of a page that must be fetched for its noindex directive to be seen. Verify exact user-agent, path and environment behavior.
Audit templates before individual URLs
Status codes
Redirect chains/loops
Canonical format
Robots directives
Sitemap membership
Internal link hrefs
Pagination/facets
Mobile rendered content
JavaScript links/content
Hreflang where used
Duplicate parameters
Soft 404 behavior
HTTPS/host consistency
Orphan URLs
On-page means relevance and comprehension
Element
Question
Title/main heading
Does it accurately summarize the page without stuffing or bait?
Body content
Does it answer the actual need with original useful evidence and clear structure?
Links
Can users and crawlers reach relevant supporting pages through descriptive links?
Media
Does important visual information have useful text alternatives/context?
Structured data
Does valid markup describe content visibly present and follow feature policies?
Authorship/trust
Are creator, business, sourcing and update context clear where relevant?
Use Search Console as evidence, not an oracle
URL Inspection can show the indexed version, selected canonical and crawl/index details for a URL. Performance reports aggregate query/page/country/device/search-appearance data with privacy and reporting limits.
Absence of a query does not prove no one searched it; low-volume data may be withheld. Indexing is not guaranteed merely because a URL is valid.
Prioritize by template and business importance
A canonical bug across every product is usually more important than a missing description on one low-value page. Estimate affected URL set, journey importance and evidence confidence.
After changes, verify server output, rendered DOM, live test and later index/performance evidence rather than closing the task when code ships.
Real-world example
Example: category pages disappear from search
Example
The sitemap lists category URLs, internal links point to them, but a template update added noindex while robots.txt blocks the paths. The audit identifies contradictory intent, removes the inappropriate crawl block, corrects the directive, validates rendered output and monitors indexing—without promising rankings.
Try this
Trace one priority URL
Record discovery link, sitemap state, robots access, HTTP status, rendered main content, meta robots, canonical, Search Console indexed state, title/H1, internal links and intended outcome. Highlight contradictions.
Common questions
Questions beginners ask.
What is a technical SEO audit?
A review of the systems that affect discovery, crawling, rendering, canonicalization, indexing and search presentation.
Does robots.txt remove a page from Google?
Not reliably. It controls crawling; an already known blocked URL can still appear without content. Use suitable access control or noindex where appropriate.
What is a canonical URL?
The representative URL selected for a group of duplicate or very similar pages; declared signals are hints and should be consistent.
Should every URL be in the sitemap?
Include canonical URLs the site wants indexed, not redirects, errors, duplicates or intentionally non-indexable pages.
Does valid structured data guarantee a rich result?
No. It creates eligibility when content and policies qualify, but appearance remains at Google’s discretion.
What is a soft 404?
A page that returns a success status but effectively says content is missing or has little useful content.
Can JavaScript content be indexed?
Google can render JavaScript, but fetching, rendering, timing and implementation can create risks; important content and links should be testable.
Does indexing guarantee ranking?
No. Indexing makes a page eligible; relevance, quality, competition and many systems affect visibility.
