Skip to main content
SiteScan.top

SEO check in 15 minutes: a step-by-step checklist

An SEO check you can finish in 15 minutes: indexing, robots.txt, canonicals, titles and descriptions, sitemap, speed, structured data and broken links.

SEO · Published: 11 October 2026 · 5 min read · Ольга Мирошник

A full SEO audit takes days, yet most disasters are visible in a quarter of an hour. A section blocked from indexing, a canonical pointing at staging, the same title on a hundred pages, a sitemap full of 404s — none of these need deep expertise, only someone who looks in time. Below is an SEO check split by the minute: a timer, a scanner report, a browser and one terminal. The goal is not a perfect site but a short list of what to fix first.

Minutes 0–2: start the scan

Let the machine work while you read on. Enter the domain in the free scan form on the home page: the crawler walks the pages, checks the service files and asks Google PageSpeed for the home page's speed data. Meanwhile, open the site in a private window — everything you check by eye should match what the crawler sees.

Minutes 2–4: is indexing open?

The most expensive mistake is a site that asks search engines to leave.

  1. Open /robots.txt. Is there a Disallow: / for User-agent: * or for Googlebot specifically? Does it name the sitemap? The help page on robots.txt lists what else to look for.
  2. Look at the "SEO diagnostics" block of the report. It separates intentional noindex (cart, account, search — fine) from mistaken noindex: a product, category or article hidden from search. The second kind is ticket number one.
  3. Search for site:example.com. The count is rough, but if you expect a thousand pages and see twelve, the problem is not your content.

Minutes 4–6: one address per page

Open the source of a few key pages (Ctrl+U) and find rel="canonical". Typical misses: it points to the http version, another host, a redirect or another language. The report groups these as "No canonical" and "Wrong canonical"; why it matters is covered in our guide to canonical URLs. While you are there, confirm that http:// and www reach the main address in a single 301.

Minutes 6–8: titles, descriptions, H1

Scroll through the pages table in the report — it shows the title, description, headings and canonical of every page. Look for:

How to write meta tags people actually click is in our piece on titles and descriptions.

Minutes 8–10: the sitemap

Open /sitemap.xml. A good sitemap is valid XML with only canonical URLs that answer 200 — no staging, no sorting parameters. The report also flags canonical addresses missing from the sitemap: a page asks to be indexed at an address the sitemap never mentions.

Minutes 10–12: speed and mobile

Check the PageSpeed Insights block: mobile and desktop results and Core Web Vitals. Google's thresholds are LCP ≤ 2.5 s, CLS ≤ 0.1 and INP ≤ 200 ms. If real-user data (CrUX) is there, trust it over the lab run, which only simulates. Then look at the mobile layout: viewport, horizontal scrolling, tap targets — see mobile usability.

Minutes 12–14: markup and languages

Paste a product or article URL into the Schema.org validator or Google's Rich Results Test: are Product, Article, BreadcrumbList and Organization present and error-free? More in our article on structured data. On a multilingual site the report adds a "Language versions" block: hreflang reciprocity, x-default, language codes and canonicals that agree.

Last look: internal links, how many were checked and how many are broken. Every link to a 404 wastes link equity and leads crawlers into a dead end; how to find and fix them is in our guide to broken links. Now write down the findings in order of impact: indexing, then canonicals and duplicates, sitemap, speed, markup.

What next

A 15-minute SEO check catches the emergencies; it does not replace working through the ranking factors. Once the fire is out, move on to a systematic SEO website analysis. And instead of retyping the checklist, use "Copy fix brief" in the SiteScan report to hand the critical, high and medium findings to a developer — then rescan after the fixes to see what really went away.

Read next

Check how much of this is on your own site

A free scan surfaces broken links, JS errors and performance problems in about a minute.