Pre SEO Site Analysis Report Template

Think of this template as a pre-flight checklist for a new SEO project. You are not fixing anything yet; you are gathering facts so you know where to put your time and how to measure progress later. I once ran a pre-analysis for a 5,000-page e-commerce site. The template revealed 1,200 pages had no internal links (orphans), 800 returned 404s, and the top 30 pages drove 90% of organic revenue. Without the template, I would have started optimising product pages that did not matter.

Some people argue that a detailed template is wasted time when you could just fix obvious issues. But I have found that without a baseline you cannot prove ROI or show a client what changed. The template gives you a single source of truth. My decision rule is simple: if the site has fewer than 50 pages and no complex technical setup, skip the template and use a quick checklist. For anything larger, invest two hours in the template — it pays back when you need to explain why you prioritised one fix over another.

The template does not have to be fancy. A spreadsheet with columns for issue type, severity, affected URLs, and recommended action is enough. The act of filling it in forces you to look at every corner of the site. That is where the real insights come from.

The template matters most in three situations. First, when you start a new SEO project for a client or your own site — you need a baseline to measure progress. Second, before a site migration or redesign, because you want to know what is working now so you do not break it. Third, when you inherit a site with no prior SEO work — the template helps you quickly spot the worst problems.

I have used this template on over 20 projects, and it consistently surfaces two or three issues that would have derailed optimisation if missed. For a recent migration, I ran the template before and after. The before template listed 14 critical issues (broken redirects, missing [canonical tags](/canonical-tag/), and a misconfigured [robots.txt](/robots-txt/)). After the migration, only three critical issues remained. The client could see exactly what had improved.

But there is a counter-argument: for a one-person team on a tight deadline, a full template can feel like overhead. In that case, at least do the crawl and the top-pages analysis. Skip the backlink or competitor sections if necessary. The template is flexible — you can strip it down to a single sheet of essential checks. The important thing is to have a structured process rather than jumping straight into optimisations. I also use the template as a handover document when I pass a site to another SEO practitioner.

An edge case: if the site is brand new with very few pages, the template still applies but you will focus on indexability and technical foundations instead of legacy issues. For a new site, the template becomes a launch checklist.

I used to start every project by pulling traffic and keyword data from GA4 and GSC. That took hours and gave me a false sense of health. On one site, traffic looked stable, but the crawl revealed 50% of pages were set to noindex because of a stray [directive](/directive/) in the theme. I now always run a crawl first — it catches technical problems that metrics alone hide. The crawl is the foundation of the template.

My second mistake was including too many URLs. Early templates listed every single page. A 10,000-page site produced a 200-page report no one read. Now I focus on the top 20 pages by traffic or conversions. That is where the leverage is. If there is a [duplicate content](/duplicate-content/) issue, it usually shows up in those pages first. I also learned to group technical findings by type rather than listing each URL individually. A table that says "3,000 pages have missing meta descriptions" is more useful than three thousand rows.

I also assumed the template had to be the same for every project. Now I tailor it: e-commerce sites need product page checks, lead-gen sites need landing page analysis. The one-size-fits-all approach wasted time and produced irrelevant data. The final admission: I used to skip the executive summary because I thought technical clients wanted raw data. But even developers appreciate a one-page summary of the top three actions. It forces me to decide what really matters.