Website SEO Audit Checklist

A website SEO audit is a practical pass over fetch, query match, and conversion — in that order — not a 90-point theater report. If Google cannot retrieve the page, rankings do not matter. If the page retrieves and answers the wrong job, rankings will disappoint. If the page ranks and the visitor cannot enquire, you audited the wrong finish line. Skip the decorative PDF. Use a short checklist you can run twice: once to find work, once to confirm you shipped it.

The technical half of fetch lives in the technical SEO guide. The writing half lives in the on-page SEO guide. If a page should rank and does not, read why a website is not ranking after you have ruled out “Google never saw it.” Tools that help without inventing a grade are listed in SEO tools for small businesses.

Fetch and index

Start in Google Search Console, a free public product. Verify the property that matches the canonical host. Inspect the home page, each money service URL, and contact. A 404, a redirect loop, or an accidental noindex on a live service page is an audit finding. A blog post that is “Discovered — currently not indexed” is usually a lower priority.

Then confirm the boring files. Robots.txt should not block the templates you want indexed. A sitemap should list canonical URLs you actually serve, not staging hosts or parameter copies. HTTP should redirect to HTTPS once, and www versus apex should settle on one host. Pagination, faceted filters, and search-result URLs on the site should not create an infinite crawl of thin copies. If you recently migrated, check that old money URLs 301 to the new equivalents — not to the home page as a habit.

View the money pages as Googlebot would: text in HTML, titles that exist, status 200. A crawler helps after a CMS change when the mistake is in a template you will not click. Record fetch issues in a list you will close. Do not mix them with “we should blog more.”

Query match

For each URL that can be fetched, write the query it should win — the job a buyer would type — and read the first screen. If the heading and opening paragraph answer a different job, the page is not ready to rank for the one you wanted. Search Console’s query report tells you what Google already associates with the URL. If that association is reasonable, improve the page for those queries. If it is a mismatch, change the page or split the job. Do not hide the real topic behind a slogan.

Check titles and headings as writing, not as a score. The meta preview is a length aid; Google may still rewrite the title. Two service pages that say the same thing with different city names swapped in are a quality problem, not a coverage strategy.

Thin or scaled pages belong on the cut list. Google’s spam documentation warns against pages whose main purpose is manipulating rankings. An audit that recommends “add 50 location URLs” without unique information is a content-farm brief, not an SEO audit.

Conversion path

A page that matches a query still fails if a visitor cannot take the next step. On each money URL, find the action: call, form, book, buy. Click it on a phone. Submit a test. Confirm it arrives. If the audit never leaves Search Console, you will ship indexable pages that do not make the phone ring. That is the same finish line as conversion work: name the action, remove the obstacle.

Look for leaks that pretend to be design: a slider that rotates the offer away, extra form fields, a phone number that is only an image, a quote button that opens a chatbot with no transcript. Fix those in the same sprint as fetch issues on the same URL.

Proof should be checkable — entity details, a named person, hours you answer — not invented testimonials. Scriplit is a Wyoming LLC founded by Adnan Sami on 9 October 2024; (901) 401-0039 and contact@scriplit.com are published because they are used.

1. Verify Search Console on the canonical host and open URL inspection for home, core services, and contact.
2. Record fetch failures: 4xx/5xx, redirect chains, blocked robots rules, accidental noindex or canonical to the wrong URL.
3. Confirm HTTPS, host canonicalization, and that the XML sitemap lists live canonicals only.
4. For each money URL, write the query job and check that the first screen answers it.
5. Compare Search Console queries for those URLs against the copy; note mismatches to rewrite or split.
6. Check titles, headings, and internal links for clarity — not for a density percentage.
7. List thin, duplicate, or scaled URLs to improve, merge, or remove.
8. On the same money templates, check field Core Web Vitals in Search Console or PageSpeed Insights; treat a poor LCP, INP, or CLS as a usability finding, not a vanity score.
9. Click the primary conversion on a phone; submit a test and confirm delivery.
10. Note form, call, and booking failures as audit items on the same list as crawl errors.
11. After fixes, request indexing for changed money URLs and re-inspect; do not recrawl the whole web for a title edit.

Recrawl after changes

Google does not read your mind when you ship. After you fix a money URL, use URL inspection and request indexing if the page is important and the change is real. Update the sitemap if you added or retired URLs. Keep staging noindexed. Do not submit the entire site for recrawl because you changed a footer. Recrawl is a scarce attention request; spend it on the pages that take work.

Then wait long enough to see Search Console move. A week of impressions is not a verdict. If a coverage error remains after you “fixed” it, the fix may not be on the URL Google fetches. Re-inspect the live HTML.

Run the next full pass after a redesign or CMS change, and about quarterly on a stable small site. When you want the pass done and the fixes implemented, that is SEO services. Send the URL, Search Console access if you have it, and which pages take enquiries through the SEO contact form.

FAQ

How often should I audit?

After a redesign, after a CMS change, and on a quarterly pass for a small site. Daily audits of the same issues are procrastination. If you ship something that can break fetch — a new theme, a new host, a new robots file — run the fetch steps again that week.

What is a crawl error versus a quality issue?

A crawl error means the page could not be fetched as intended (blocked, broken, redirected into a loop, wrong host). A quality issue means the page fetched fine and still should not rank: thin, mismatched to the query, scaled, or unhelpful. Do not mix the two in one panic. Fix fetch first, then decide whether the page deserves to exist.

Should I pay for an audit?

Pay if you want someone to implement or to inspect a messy site you cannot see clearly. A PDF of generic advice you already knew is not worth much. The useful deliverable is a short list of URLs, the problem on each, and the change that closed it — plus a working conversion path on those same URLs.