If you’re searching for a seo audit checklist you can actually use (not a 60-page report nobody reads), this template is built for one goal: turn findings into fixes. We’ll focus on Technical Health first, then content and links, and finish with a simple way to prioritise and ship improvements. If you want to sanity-check your baseline before you start, review these common technical SEO mistakes companies make so you don’t waste time auditing the wrong things.
This checklist is written to work whether you’re auditing a small brochure site or a large e-commerce platform, and it includes the tools to use, what “good” looks like, and what action to take when something fails.
How to use this audit (so it becomes actions, not a long report)
Before you crawl anything, set up a workflow that forces output to become work items.
- Create a single spreadsheet with tabs for Technical, Content, Links, and a final “Action Plan”.
- Every issue must include: affected URL(s), evidence (screenshot/export), severity, recommended fix, owner, and a retest method.
- Write tickets as acceptance criteria (what will be true when this is fixed), not as observations.
Audit rule: if you can’t describe how to fix it and how you’ll verify it, it doesn’t belong in the final deliverable.
Your minimum tool stack
You can do a strong audit with a lightweight set of tools:
- Google Search Console (indexing, coverage, performance queries, sitemaps)
- A crawler (Screaming Frog, Sitebulb, Ahrefs audit, etc.)
- Page performance (Lighthouse / PageSpeed Insights / CrUX where available)
- Backlink tool (Ahrefs, Majestic, Semrush, etc.)
- Analytics (GA4 or equivalent) for engagement and conversions
Section 1: Technical Health (the foundation)
Technical Health answers one question: can search engines efficiently crawl, render, and index the right pages, and can users access them quickly and reliably?
1) Crawlability: can bots access the site?
Start with crawling and robot controls. Use your crawler plus Search Console.
- Robots.txt
- Check: important directories/pages are not blocked; staging rules are not deployed to production.
- Tool: robots.txt file + Search Console inspection.
- Action: remove unintended Disallow rules; keep targeted blocks for low-value parameter paths.
- Reference: align with Google’s robots.txt documentation when updating syntax and intent.
- XML sitemap(s)
- Check: only canonical, indexable URLs included; fresh lastmod dates; no 3xx/4xx/5xx URLs.
- Tool: crawler + Search Console Sitemaps report.
- Action: regenerate sitemaps from the canonical URL set; split by type (pages, categories, products, blog) for large sites.
- Reference: follow Google’s sitemap guidelines for best practice formats and limits.
- Navigation and internal discovery
- Check: key pages are reachable within a reasonable click depth; no orphan pages that should rank.
- Tool: crawler “Orphan pages” + analytics landing pages + Search Console indexed pages.
- Action: add contextual internal links from relevant hubs; ensure category and subcategory structures reflect how users search.
2) Indexability: are the right pages eligible to rank?
This is where many audits go wrong: teams fix “errors” but don’t confirm whether the page should be indexed at all.
- Meta robots and X-Robots-Tag
- Check: intended pages are index, follow; low-value pages (filters, internal search) are noindex where appropriate.
- Tool: crawler indexability reports.
- Action: define an “indexation policy” (what types of URLs should be indexable) and implement consistently.
- Canonicalisation
- Check: self-referencing canonicals on canonical pages; canonicals not pointing to redirected/404 pages; parameterised duplicates handled.
- Tool: crawler canonical reports.
- Action: consolidate duplicates with canonical tags and/or redirects; reduce internal links to non-canonical variants.
- Search Console indexing signals
- Check: “Crawled – currently not indexed”, “Discovered – currently not indexed”, and soft-404 patterns for templates.
- Tool: Google Search Console Indexing reports.
- Action: improve content uniqueness and internal linking for valuable pages; noindex thin/duplicated pages that should not rank.
3) Status codes and redirects: is link equity leaking?
Fixing status code hygiene usually produces fast gains because it improves crawl efficiency and user experience.
- 4xx errors (broken pages)
- Check: 404s receiving internal links or backlinks; broken resources (images, JS, CSS).
- Tool: crawler + backlink tool for “broken backlinks”.
- Action: restore the page if it should exist; otherwise 301 to the closest equivalent; update internal links at the source.
- 5xx errors (server reliability)
- Check: spikes in 500/502/503 during crawls; timeouts and TTFB issues.
- Tool: server logs, hosting monitoring, crawler.
- Action: fix application errors; implement caching/CDN; ensure stable capacity for peak traffic and bot activity.
- Redirect chains and loops
- Check: more than one hop; protocol/hostname/trailing slash inconsistencies.
- Tool: crawler redirect reports.
- Action: update rules so every old URL 301s directly to the final destination in a single hop; standardise URL format.
4) Site architecture & URL quality: can the site scale without duplication?
Architecture issues create “hidden” technical debt: they multiply duplicate pages, dilute internal links, and confuse indexing.
- URL patterns
- Check: clean, descriptive paths; consistent lowercase; minimal parameters for indexable pages.
- Tool: crawler + manual sampling.
- Action: create standards for category/product/blog URLs; keep tracking parameters out of canonical URLs.
- Pagination and faceted navigation
- Check: infinite combinations generating thin/duplicate pages; parameter pages getting indexed.
- Tool: crawler (parameter reports), Search Console URL inspection samples.
- Action: decide which filters deserve indexable landing pages vs. noindex; ensure paginated series are crawlable and internally linked.
5) Rendering & JavaScript: can Google see the content?
If a page “looks fine” to users but content is injected late via JavaScript, search engines may index an incomplete version.
- Check: key content and internal links appear in the rendered HTML; primary copy isn’t hidden behind interactions; lazy-loaded content is accessible.
- Tool: crawler with JavaScript rendering + Search Console URL inspection (rendered page) + manual view-source vs. inspect element.
- Action: server-render critical content; hydrate progressively; ensure internal links are present in the initial render where possible.
6) Performance & Core Web Vitals: are users getting a fast experience?
Performance is technical health with direct business impact: it affects crawl efficiency, UX, and conversions. If you need a region-specific lens, see Core Web Vitals optimisation in Dubai for common patterns on high-traffic sites.
- Core Web Vitals
- Check: LCP, INP, CLS at template level (home, category, product, blog) rather than only on a few URLs.
- Tool: PageSpeed Insights, Lighthouse, and real-user data where available (CrUX / Search Console CWV report).
- Action: prioritise the worst templates; fix biggest offenders first (hero image sizing, render-blocking resources, heavy third-party scripts, layout shifts).
- Image and media efficiency
- Check: next-gen formats, responsive sizing, lazy loading below the fold, correct aspect ratios.
- Tool: Lighthouse audits + manual network waterfall sampling.
- Action: compress and resize; use CDN image transformation; reserve space to avoid CLS.
- Third-party scripts
- Check: chat widgets, heatmaps, tag managers, and tracking pixels increasing INP and blocking the main thread.
- Tool: Lighthouse performance trace.
- Action: remove or defer non-essential scripts; load conditionally; audit tags quarterly.
7) Mobile-first readiness: does the mobile version contain everything that matters?
- Check: parity of primary content, internal links, structured data, and meta tags between mobile and desktop.
- Tool: responsive testing + Search Console URL inspection for rendered output.
- Action: ensure mobile templates aren’t “trimmed” in ways that remove SEO-critical elements.
8) Structured data: can search engines understand entities and page types?
Structured data won’t rescue weak pages, but it reduces ambiguity and improves eligibility for rich results where applicable.
- Check: valid schema types for your page templates (Organization, LocalBusiness, Product, Article, FAQ where appropriate), and no spammy markup.
- Tool: Rich Results Test + Schema validator + crawler extraction.
- Action: add schema at template level; ensure it matches visible content; fix errors and warnings that block eligibility.
9) Security & HTTPS: is the site trustworthy and consistent?
- Check: all URLs resolve to HTTPS; no mixed content; correct canonical host (www vs non-www); HSTS where appropriate.
- Tool: crawler + browser security console.
- Action: 301 everything to the preferred HTTPS host; eliminate insecure resources; renew certificates reliably.
10) Log files (optional but powerful): what are bots actually doing?
Log file analysis is where you find crawl budget waste and “important pages not being crawled” issues with evidence.
- Check: high crawl activity on parameter URLs, low crawl frequency on key money pages, repeated hits on 404/5xx, slow response times for bots.
- Tool: server logs + log parser (or BigQuery pipelines for large sites).
- Action: block low-value patterns, improve internal linking to key pages, and fix server performance bottlenecks.
Section 2: Content audit (what to keep, improve, merge, or remove)
The content audit is not “count the words”. It’s a decision-making system: does each page deserve to exist, and is it the best answer for its query?
1) Inventory and segmentation
Export all indexable URLs, then segment by template and intent.
- Segments: brand pages, service pages, category pages, product pages, blog posts, location pages.
- Metrics to pull: impressions, clicks, CTR, average position (GSC), sessions and conversions (GA4), backlinks (if relevant).
2) Search intent alignment and on-page basics
- Title tags and meta descriptions
- Check: unique titles; primary topic match; avoid truncation; meta descriptions support CTR (even if not a ranking factor).
- Action: write titles by template rules; prioritise top-traffic URLs first.
- Headings and content structure
- Check: single clear H1; logical H2/H3 sections; scannable sections answering common questions.
- Action: restructure long pages into sections; add comparison tables, FAQs, or step-by-step subsections where it improves clarity.
- Content depth and uniqueness
- Check: thin pages, templated boilerplate, near-duplicates across locations or categories.
- Action: merge overlapping pages (reduce cannibalisation), expand pages with real subject coverage, or noindex/remove pages with no strategic value.
3) E-E-A-T signals (practical checks)
For pages where trust matters (finance, healthcare, legal, high-value services), add proof and reduce ambiguity.
- Check: author attribution, editorial review process, company contact info, case studies, citations, policies (refunds, privacy), and up-to-date facts.
- Action: add author boxes and “last reviewed” dates, strengthen about/contact pages, and include evidence (photos, credentials, data sources) where relevant.
4) Internal linking within content (content-led discoverability)
Content doesn’t rank in isolation; it needs internal links that reflect real topic relationships. Ensure every strategic page has:
- At least 3–10 contextual links from related pages (not only header/footer).
- Anchors that describe the destination (avoid repeating the same exact anchor sitewide).
- A logical hub-and-spoke model where one hub page links to supporting pages and receives links back.
Section 3: Link audit (quality, risk, and leverage)
A link audit should do two things: protect you from obvious risk and reveal the fastest authority wins.
1) Backlink profile quality
- Check: relevance of linking domains, natural anchor text distribution, sitewide/footer link patterns, and unusual spikes in links.
- Tool: Ahrefs/Semrush/Majestic exports.
- Action: tag links by type (editorial, directory, PR, partner, UGC). Focus efforts on replicable, relevant editorial wins.
2) Toxic link risk (keep it calm and evidence-based)
Most sites have some low-quality links. The goal is to spot patterns that correlate with ranking drops or manual actions, not to panic-disavow everything.
- Check: clusters of irrelevant foreign-language domains, obvious link networks, malware-infected sites, or aggressively exact-match anchors.
- Action: attempt removals for clear spam; maintain a disavow file only when justified by strong evidence and risk profile.
3) Internal link equity flow (often the easiest win)
Use your crawler to identify pages with high internal authority and ensure they pass value to priority pages (services, categories, conversion pages).
- Check: high-authority blog posts that don’t link to commercial pages; important pages buried deep; excessive links to low-value pages.
- Action: add internal links from relevant high-traffic pages to priority pages; clean up navigation to reduce dilution.
Your action-first audit template (copy into a spreadsheet)
Use these columns so your audit output becomes an implementation plan:
- Area: Technical / Content / Links
- Issue: short name (e.g., “Redirect chains on category pages”)
- Evidence: export name + row numbers, screenshot, or GSC report
- Scope: number of affected URLs + templates involved
- Impact: High / Medium / Low (traffic, revenue, crawl, UX)
- Effort: High / Medium / Low (dev complexity, content time)
- Recommendation: single clear fix
- Owner: SEO / Dev / Content / PR
- Due date: realistic target
- Retest: how you’ll confirm (crawl delta, GSC validation, PSI improvements)
A simple prioritisation rule (Impact × Effort)
When the audit is done, sort issues into four buckets:
- High Impact / Low Effort: do these first (quick wins).
- High Impact / High Effort: plan as projects (roadmap).
- Low Impact / Low Effort: batch later (maintenance).
- Low Impact / High Effort: usually defer or drop.
What to deliver: a one-page action plan (not a massive deck)
Your stakeholders don’t need everything you checked; they need what to do next. Aim to ship these deliverables:
- Top 10 issues with expected outcomes (crawl, indexation, rankings, conversions).
- A 30/60/90-day plan tied to owners and release cycles.
- A retest schedule (e.g., recrawl weekly for 4 weeks; recheck GSC validations; monitor CWV monthly).
30/60/90-day example plan
Days 1–30: fix indexation blockers (robots/noindex mistakes), remove redirect chains, repair 404s with internal links, and clean sitemap/canonicals.
Days 31–60: tackle performance on worst templates (LCP/INP/CLS), implement structured data fixes, and address thin/duplicate content on priority pages.
Days 61–90: strengthen internal link hubs, launch a focused link acquisition campaign for priority pages, and run a second audit crawl to confirm improvements.
When to bring in help
If your audit reveals platform-level problems (rendering, faceted navigation, internationalisation, CWV template issues), it’s often faster to solve with specialist support. If you’d rather have the technical side handled end-to-end, explore our technical SEO Dubai services for implementation-led audits and fixes.
FAQs
How often should I run an SEO audit?
Run a lightweight technical crawl monthly (or after major releases), and a deeper audit quarterly. For large e-commerce sites with frequent changes, monitor key technical health signals weekly.
What’s the difference between a technical audit and a content audit?
A technical audit checks whether search engines can crawl, render, and index your pages efficiently (and whether the site performs well). A content audit decides whether each page is the best answer for its target queries, and what to improve, merge, or remove.
Should I fix everything the crawler flags?
No. Crawlers are great at finding symptoms. Use an indexation policy and prioritise by impact. For example, a “missing meta description” on a low-value page is rarely urgent, but a canonical pointing to a redirected URL can be a serious technical health issue.
What are the fastest technical wins?
Common fast wins include removing redirect chains, fixing internal links to 404 pages, cleaning XML sitemaps so they only include canonical indexable URLs, correcting accidental noindex/robots blocks, and improving performance on high-traffic templates.
How do I prove the audit worked?
Define success metrics before you start: improvements in indexed canonical pages, reduced crawl waste, fewer GSC errors, better CWV on key templates, and measurable lifts in impressions/clicks/conversions for prioritised pages. Then retest using the same crawl settings and compare before/after exports.