SEO analysis: how to run a 30-minute site analysis
A 30-minute SEO analysis flow: indexing, speed, titles, queries and internal links, using free tools to find which problem to fix first.
By Roozbeh Nazari · CEO
When you look at a site for the first time, you rarely have the time or budget for a full audit. This article is written for that situation: an SEO analysis flow that fits into 30 minutes, runs on free tools and ends with an answer to "what should we fix first?" The goal is not to find every problem; it is to see the most expensive problems early. When you need a comprehensive check, move on to the 20-item technical SEO audit checklist; the flow here is the quick way to decide whether that audit is needed. We split the flow into six steps; each takes about five minutes and ends with a one-line note.
Preparation: the access an SEO analysis needs
Before you start, open three things: the site's Google Search Console property, PageSpeed Insights and the site itself in a browser. If you have no Search Console access, the analysis can still be done, but the indexing and query steps will rest on estimates; write that down clearly in your notes. Also open a notes file with six headings: indexing, speed, page structure, queries, internal links, priority. The most common mistake in an SEO analysis is pouring findings into one long list and then being unable to tell which ones matter. The headings make that separation from the start. You can also keep our free tools in a side tab for quick checks of meta tags and page speed; they all run in the browser and need no sign-up.
Minutes 0–5: indexing status
The first question is simple: does Google see the site's important pages? The Page indexing report in Search Console shows how many URLs have been crawled and indexed, and the reasons pages were not indexed. Google's own help page also suggests a simple site: search instead of this report for sites with fewer than 500 pages. In these five minutes, look at three things: whether an important service or product page is among the pages not indexed; whether unexpected URLs appear under "Excluded by noindex tag" or "Blocked by robots.txt"; and whether duplicate-page warnings point to confusion in canonical selection. A problem here outranks every other step, because improving the title of a page that is not in the index produces nothing. We describe the detailed diagnosis flow for this step in our Search Console guide.
Minutes 5–10: speed and field data
Enter the home page and one high-traffic inner page into PageSpeed Insights. The report shows two kinds of data: field data from real users covering the previous 28-day period, and lab data that Lighthouse produces in a controlled environment. In a quick site analysis, look at field data first; whether LCP, INP and CLS are within their thresholds describes the real experience. If there is no field data, that is a finding too: the site either does not get enough traffic or falls outside measurement. Do not interpret the lab score on its own; the two data sources can contradict each other, and that is normal. Write one line in your notes: "field data good / borderline / poor / none" and which metric has the biggest problem.
Minutes 10–15: titles and page structure
Now choose five pages: the home page, two service or category pages, one blog post and a contact page. On each, check the page title, the meta description and the H1. What you are looking for: different pages carrying the same title, meta descriptions that come from the template and repeat on every page, pages with no H1 or with more than one H1, and titles that do not say what the page is about. A five-page sample does not represent the whole site, but it almost always catches template-driven problems, because a template error is not on one page but on every page that uses that template. If you see a problem, note the page type, not individual URLs.
Minutes 15–20: queries and intent match
In Search Console's Performance report, select the last three months and sort queries by impressions. Look for two patterns. First, queries with high impressions but a low click-through rate: the page is visible, but the title and description in the search result are not earning the click. Second, queries landing on the wrong page: a blog post showing for a service query, or a sales page showing for an informational query. The second pattern usually comes from internal structure and is not solved by a single content fix. Do not get stuck on ranking positions at this step; average position varies with personalisation and location. What matters is the intent with which the site is being seen and whether that matches the business goal.
Minutes 20–25: internal links and structured data
Starting from the home page, count how many clicks it takes to reach the most important service page. If important pages sit several clicks deep or only get links from the menu, they need contextual links from within content. Also check whether links are real anchor tags; buttons that work only through a JavaScript event are not links to a crawler. Then run one page through Google's Rich Results Test and see whether the structured data throws errors or contradicts the content on the page. At the end of this step you write two lines: is there an internal linking problem, and is structured data in use?
Minutes 25–30: prioritising the findings
The last five minutes matter most. Give each finding in your notes two labels: impact (does it affect the whole site, one template or a single page) and effort (can the content team fix it, or is a developer needed). Set the priority in this order: indexing problems first, then template-driven problems, then intent mismatch, and single-page improvements last. This order is a rule we have observed in practice: content work done before indexing and template problems are fixed often fails to show its effect. Your output is a three-item list; if more than three "urgent" items come out, that tells you that you have reached the limit of the 30-minute SEO analysis flow and a full audit is needed.
The limits of a quick analysis
This flow does not replace a crawling tool. A five-page sample will not reveal thousands of unnecessary URLs generated by pagination and filter parameters, broken internal links or hreflang errors on multilingual sites. The backlink profile, content quality and competitor comparison also fall outside this half hour. The value of a quick SEO analysis is that it asks the right question: "Does this site need deep work, and if so, where should it start?" When deep work is needed, we run crawling, log analysis and template-level fixes as part of our technical SEO service. No analysis on its own guarantees a particular ranking outcome; an analysis only clarifies where effort should go.