Website SEO Audit Checklist

Website SEO Audit Checklist

1) Audit Scope, Goals, and Benchmarks

Start with a clear audit scope. Pick 10 to 50 priority pages first, not the whole site, unless the site is tiny. The best audit answers one question: which pages need attention before they lose traffic or miss conversions?

List the page types you care about: product pages, category pages, landing pages, blog posts, and the checkout or lead form path. A homepage can look healthy while a pricing page leaks leads, so name the exact templates and the exact conversion paths you want to inspect. One page can hide a larger pattern.

Record current rankings, traffic, and index coverage before touching anything. If a migration happened in the last 90 days, note it. If a new section launched in Q2, note that too. These dates matter because a sudden drop may be the side effect of a release, not a search problem.

A useful audit also sets a baseline for later comparison. Save the date, the export source, and the owner of the report. Without that, a month later you are guessing. That gets expensive fast.

If the team already tracks properties in Astrina, keep the audit sources in one place so you can compare pages, dates, and status changes without copying tabs around. For a quick starting point, the dashboard view helps centralize the site list before the audit begins.

2) Technical SEO Checklist

Technical work comes first because content fixes do little if crawlers cannot reach the page. Test robots.txt and meta robots directives on the pages you expect to rank. A single disallow line can block a whole section. Yes, that still happens.

Next, look for broken links, redirect chains, and 4xx/5xx errors. A chain of three redirects adds delay and risk; a 404 on a linked page wastes both crawl budget and user trust. Check the most visited templates first, then the long tail. A single broken nav link can create hundreds of bad clicks.

Validate XML sitemaps and canonical tags. The sitemap should list live, indexable URLs, and the canonical should point to the preferred version of each page. If the sitemap contains parameter URLs or the canonical tag points somewhere else, search engines get mixed signals. Mixed signals slow discovery.

Review Core Web Vitals and mobile usability. A page can rank and still feel slow on a phone. Check LCP, INP, and CLS on template groups, not only on the homepage, because the homepage often gets the cleanest code and the most attention. One product page with a heavy hero video can pull down the whole template.

Also check HTTPS, duplicate versions, and URL consistency. The site should resolve the same way every time: http to https, non-www to www or the reverse, trailing slash rules, and uppercase versus lowercase all handled consistently. One site I saw had four visible versions of the same URL. That is not a small issue.

Technical checks should include one direct crawl of the site and one manual pass through the highest-value pages. Crawlers miss context, and humans miss patterns. Together they catch more. They usually catch the redirect loop too.

3) On-Page Content Audit

Each important page needs a clear match between search intent and content. If the query is informational, the page should answer questions quickly. If the query is commercial, the page should show product detail, proof, and next steps. Do not make a service page read like a blog post unless the intent calls for that format.

Titles, H1s, headings, and meta descriptions should be reviewed page by page. The title should say what the page is, not what the company wishes it were. The H1 should support the title, not repeat it word for word. Headings should break the page into sections a real person can scan in under 30 seconds.

Remove thin, duplicated, or outdated content. A 150-word page copied across 20 city pages will usually underperform, and it can dilute the site’s quality signals. If a page no longer serves a clear purpose, either improve it or archive it. Leaving it untouched is rarely the right choice.

Add internal links to supporting pages where they help the reader move from one step to the next. A product page may link to setup instructions, and a guide may link to a pricing page. If the path matters, the link matters. For teams that want to compare page groups while reviewing content, a pricing page often becomes a useful test case because it has both search intent and conversion pressure.

Confirm images have descriptive alt text. An image of a dashboard should not be called “image1.” If the image adds meaning, describe the meaning in plain language. If it is decorative, keep the text restrained. Screen readers, image search, and compliance audits all care about this detail.

Content audits work best when they are specific. Write down the page name, the issue, and the fix. “Weak” is not enough. “Title does not include the product name” is enough.

4) Site Performance and UX Review

Speed and usability affect SEO performance because users react to them immediately. Inspect load time bottlenecks and heavy assets such as large images, uncompressed video, and bloated scripts. A page that looks elegant on desktop can stall on a mid-range phone with a 4G connection. That costs clicks.

Simplify navigation and improve click depth. If an important page takes five clicks from the homepage, the site may be making search engines work too hard and users work too hard. The goal is usually 2 or 3 clicks for priority pages. Not 7.

Mobile screens need a separate review. Tap targets should be large enough, text should not wrap awkwardly, and forms should not force users to zoom in. Check the actual phone view, not only the responsive preview in a desktop browser. Real thumbs are less forgiving than mockups.

Reduce layout shifts and intrusive interstitials. A banner that jumps the content after load can push the user to the wrong button. A full-screen pop-up on mobile can block the first interaction. If the site depends on a pop-up for email capture, test how often it appears and whether it damages the first visit. One extra step can be enough to lose the session.

Performance review should also include third-party scripts. Chat widgets, ad tags, consent tools, and analytics can all slow pages more than the core code does. Measure the page before and after each script load. If a script adds 800 ms and earns no visible value, it needs scrutiny.

Where teams manage many pages, a single dashboard view can help tie performance issues to page groups and owners. That matters when a template change affects 40 URLs at once. A manual spreadsheet can miss that pattern.

5) Off-Page Signals and Authority Check

Backlinks, mentions, and trust signals still shape visibility. Export backlink data and flag toxic or irrelevant links. The goal is not to collect links for their own sake, but to know which links support the site and which ones look random, spammy, or completely unrelated.

Compare branded search demand and referral sources. If branded searches are rising while referral traffic is flat, that can mean the brand is growing but the site is not earning links from the right places. If referrals come mostly from one source, the site may be exposed to a single partner or platform change.

Check local citations, profiles, and NAP consistency if the business serves a local market. Name, address, and phone number need to match across the website, directory listings, and profile pages. One wrong suite number or old phone line can create enough confusion to hurt leads. Local SEO is often just bookkeeping done carefully.

Authority checks should also look at where the site appears in context. A mention in a niche publication may matter more than a dozen weak directory links. Search engines are not impressed by volume alone. Neither are users.

If you need to understand how trust signals are discussed internally, a related reference like what trust score means for a website can help frame the audit findings before you decide what is actually worth fixing.

6) Daily SEO Monitoring

An audit is not finished when the report is sent. Set a daily routine to catch issues early after the audit. Check index coverage, crawl errors, and traffic drops every morning or on the same business day each week, depending on site size. The point is to spot the change before the client or sales team does.

Monitor rankings for priority keywords and pages. You do not need 500 keywords in a daily report. Ten to 20 priority terms are usually enough if they map to money pages or high-traffic content. If one of those terms drops 8 positions overnight, investigate the page, not the number alone.

Review new broken links, redirects, and page status changes. A page that moved from 200 to 302 may still work for users, but search engines treat that change differently. A batch of 404s after a CMS update is a warning, not a nuisance. Fix it before the next crawl.

Track content updates, SERP shifts, and competitor moves. If a competitor publishes a comparison page that starts ranking for your main query, note the format and the angle. If your own page slips after a title change, revert and test again. Search results can move after one edit, and you want the date tied to the edit, not to vague memory.

Log actions, owners, and next review dates. A daily note that says “fixed” is not enough. Write who changed the page, what changed, and when the next check happens. This saves hours when the same issue returns two weeks later. It often does.

Teams that review multiple sites at once tend to need one place for these daily notes. Astrina’s site-level tracking is built for that kind of follow-up, especially when a single issue affects several pages across the same domain.

7) Prioritized Action Plan and Reporting

Turn findings into a practical roadmap. Rank issues by impact and effort. A broken canonical on a high-traffic page is usually higher priority than a weak meta description on a page with no impressions. Not every finding deserves the same week of work.

Group fixes into technical, content, and authority tasks so the work can move in parallel. One developer can handle sitemap and redirect fixes while one editor updates titles and one marketer reviews backlinks. Three small lanes are often faster than one giant queue.

Assign owners and due dates for each action. If the issue is a redirect chain, name the engineer. If the issue is a thin page, name the editor. If the issue is a citation mismatch, name the local SEO owner. Ownership turns the audit from a document into work.

Summarize wins, risks, and follow-up checks in the report. A win might be “48 broken links fixed.” A risk might be “indexation still blocked on /resources/.” A follow-up check might be “re-crawl in 14 days.” Concrete numbers help leadership decide what gets budget next month.

Good reporting also makes room for one or two examples. Show the exact URL, the exact issue, and the exact fix. If the team can see the problem in one line, they can approve the change without a meeting. That saves time for the next audit.

The strongest SEO audit checklist ends with named tasks, not vague advice. If a fix needs a developer, say so. If a page needs new copy, say so. If a launch created 12 broken URLs, say that first. Then fix the URLs.