An SEO audit template structures your site analysis into repeatable, actionable sections—covering technical health, on-page optimization, content gaps, and backlink profiles. A well-designed framework ensures you catch critical issues consistently and deliver clear recommendations to stakeholders.
Start with five major sections: Technical Foundation, On-Page Elements, Content & Information Architecture, Backlink Profile, and Local/Mobile/UX. Under Technical Foundation, list crawlability checks—robots.txt, XML sitemap accuracy, canonical tags, redirect chains, orphan pages. Add server-response checks like status codes, page speed metrics from PageSpeed Insights or Lighthouse, and Core Web Vitals thresholds. On-Page Elements should enumerate title-tag length and uniqueness, meta-description presence, header-tag hierarchy, image alt-text coverage, and internal-linking density. Content & Information Architecture covers keyword mapping to URLs, thin or duplicate content flags, topical clustering, and content-gap opportunities against competitors. Backlink Profile includes domain-authority proxies, toxic-link counts from tools like Ahrefs or Moz, and referring-domain growth trends. Local/Mobile/UX captures Google Business Profile completeness for Canadian cities, mobile-usability errors in Search Console, and schema markup for relevant entity types. Each section should have a column for Page/URL, Issue Description, Severity, and Recommended Action so the output is immediately actionable.
Begin by running a full-site crawl with Screaming Frog, Sitebulb, or DeepCrawl, exporting the CSV reports for status codes, meta data, and internal links. Import those exports into your template's Technical and On-Page tabs, flagging rows where title length exceeds 60 characters, meta descriptions are missing, or canonicals point to 404s. Next, pull Search Console data—query performance, mobile-usability issues, Core Web Vitals by URL—and paste problem URLs into the relevant template rows. For backlinks, export your link profile from Ahrefs or Majestic, filter by toxic score or broken targets, and list high-priority disavow candidates. Use Google Analytics or Clarity heatmaps to identify high-exit pages or low-engagement content, then mark those URLs under Content & Information Architecture for rewrite or consolidation. If the site serves Quebec or bilingual audiences, add a Language/Hreflang subsection and verify that fr-CA and en-CA alternates are declared correctly. Annotate each finding with a screenshot or Search Console error ID so developers have context. This export-and-annotate loop turns raw tool data into a prioritized fix list.
Label every issue as Critical, Moderate, or Low based on impact and prevalence. Critical issues block indexing or tank user experience: site-wide noindex tags, broken XML sitemaps, server errors on key landing pages, mobile-unfriendly interstitials, or missing HTTPS. Moderate issues hurt rankings but don't prevent crawling: duplicate title tags across 20 percent of pages, slow Core Web Vitals on blog posts, thin content on category pages, or missing alt text on product images. Low-priority items are optimization opportunities with marginal upside: slightly long meta descriptions, internal links that could use better anchor text, or schema types you haven't implemented yet. Use color coding—red for critical, yellow for moderate, green for low—so stakeholders scan the template quickly. In client-facing templates, add an Effort column (low/medium/high) alongside Severity so they see which wins are fast. For example, fixing a robots.txt disallow is low effort and critical severity, making it the top candidate. This two-axis grid helps non-technical decision-makers allocate developer time rationally.
If you audit sites targeting Ottawa, Montreal, Toronto, or Vancouver, add rows for regional schema (LocalBusiness with CAD pricing, areaServed properties), Google Business Profile signals (category accuracy, Q&A moderation, review-response rate), and bilingual content checks. For Quebec-facing pages, verify that French translations aren't machine-generated and that hreflang tags point to the correct fr-CA URLs, not generic fr or fr-FR. Check that NAP data—name, address, phone—matches across the GBP listing, footer, and contact page, especially for multi-location businesses. Also confirm that provincial regulatory disclaimers appear where required, since missing legal copy can hurt trust signals. In the Local/Mobile section of your template, include a column for city-specific keywords in title tags and H1s, because ranking in Toronto's Local Pack often demands geo-modifiers that feel redundant on a national page. These Canada-specific rows turn a generic SEO audit example into a framework that acknowledges how Canadians search and how Google treats .ca domains in regional queries.
Once the template is populated, export a summary tab that groups issues by severity and effort, then sequence them into sprints or phases. Phase One tackles critical, low-effort fixes—robots.txt corrections, sitemap resubmission, HTTPS redirects—because they unblock crawling immediately. Phase Two addresses moderate, medium-effort items like rewriting duplicate titles, compressing images, and cleaning up redirect chains. Phase Three covers content rewrites, schema additions, and backlink outreach, which require more resources but yield compounding gains. Attach a rough timeline to each phase so stakeholders see a realistic six-to-twelve-week roadmap instead of an overwhelming list. Include a Validation column where you note the re-crawl date or Search Console screenshot proving the fix went live; this closes the loop and demonstrates progress. If you're handing off the template to a dev team, link each row to a Jira ticket or GitHub issue so nothing gets lost in email. A good SEO audit framework isn't just a diagnostic snapshot—it's a project-management artifact that turns analysis into measurable improvement.
Google's ranking signals shift, so audit your audit template twice a year. When Helpful Content or E-E-A-T updates roll out, add checklist items for author bios, publication dates, cited sources, and user-generated content moderation. When Core Web Vitals thresholds tighten, update your PageSpeed tab with the new LCP, INP, and CLS benchmarks. If Google starts surfacing passage-based results more aggressively, include a row that checks whether long-form content has descriptive subheadings and jump links. Track algorithm-update announcements from Google Search Central and SEO news sources, then map each confirmed signal back to a template row. For Canadian markets, monitor changes to how Google Business Profile attributes affect Local Pack rankings—recent additions like service menus or booking links may warrant new columns. Version-control your template in Google Sheets or Excel so you can roll back if a new section proves unhelpful, and share a changelog with your team so everyone uses the same criteria. A static template becomes obsolete within months; a living framework stays relevant and catches issues that last year's checklist would have missed.
At minimum, use Google Search Console for indexing and mobile-usability data, a crawler like Screaming Frog or Sitebulb for technical issues, and PageSpeed Insights for Core Web Vitals. Add a backlink tool—Ahrefs, Moz, or Majestic—if you want to audit link profiles. Google Analytics or Clarity helps identify high-exit pages. Free tiers of these tools cover small sites; larger portfolios need paid licenses to crawl beyond a few hundred URLs.
For sites under fifty pages, simplify the template to one tab covering technical basics, on-page titles and meta, local schema, and GBP accuracy. Skip advanced sections like log-file analysis or passage indexing. Focus on critical issues—HTTPS, mobile-friendliness, duplicate content—and moderate wins like missing alt text or slow images. A lean template prevents analysis paralysis and keeps the fix list digestible for a single developer or agency.
Yes, add a Competitive Benchmark section if you want context for content gaps and backlink opportunities. List the top three organic competitors for your primary keywords, note their domain authority, average content length, schema types, and referring-domain counts. Use that data to set realistic targets—if competitors average two thousand words per guide and you publish five hundred, flag thin content as moderate severity. Keep this section concise so it informs priorities without bloating the main checklist.
Create separate rows or a dedicated tab for French-language pages, checking hreflang implementation, translation quality, and localized keyword usage. Verify that each French URL has a corresponding English alternate tag and vice versa. For Quebec-focused sections, confirm NAP consistency in both languages and that local schema declares fr-CA. If the site auto-redirects by browser language, test that the redirect logic doesn't create orphan pages or confuse Googlebot, and document redirect rules in the Technical Foundation section.
An audit template is a deep, point-in-time diagnostic—you run it quarterly or when launching a redesign, capturing hundreds of data points across technical, content, and backlink areas. An ongoing monitoring checklist is lighter, tracking a handful of metrics weekly or monthly: organic traffic trends, Core Web Vitals pass rates, index-coverage errors, and new backlinks. Use the audit template to find and fix structural issues, then switch to the monitoring checklist to catch regressions early. Both are complementary, not redundant.
Add an Executive Summary tab at the front of your template with three sections: Critical Issues (red), Quick Wins (yellow, low effort), and Growth Opportunities (green, higher effort). For each item, write a one-sentence business impact—'Missing HTTPS loses customer trust and rankings' or 'Duplicate titles confuse Google about which page to rank.' Attach before-and-after screenshots where possible. Avoid jargon like canonical tags or hreflang unless you define them inline. Stakeholders care about revenue and risk, so frame technical debt in those terms and provide a phased timeline with expected outcomes.