Technical SEO Checklist for a Growing Website
The short answer
A technical SEO checklist covers four things: whether Google can reach and list the right pages, whether old addresses and error pages behave, whether pages load quickly and work on phones, and whether the site is free of security warnings and penalties. Run it every quarter and after every big change to the site.
Key takeaways
- Start with access. A page Google cannot fetch, or is told not to list, cannot rank, whatever else is right.
- Growth causes most technical problems: new filters, removed pages, redesigns and more people publishing.
- Most of the checks need only Google Search Console, which is free.
- Fix problems in order of how many valuable pages they affect, not by how many warnings a tool prints.
In this guide
This technical SEO checklist is for owners of websites that keep growing: more pages, more products, more people publishing. It is a list to work through with your developer, using Google Search Console. It follows the same order as our technical SEO service. Not launched yet? Use the website launch SEO checklist. About to rebuild? Use how to redesign a website without losing SEO.
Which technical SEO issues should you look for first?
The ones you can already see. Most technical SEO issues show up as a change in something you already watch.
| What you notice | Where to look | What to ask your developer |
|---|---|---|
| Pages you care about are missing from Google | The URL Inspection tool in Search Console, which gives the reason | Is anything telling Google not to fetch or list this page? |
| Visits from Google fell after a change to the site | The Page indexing report: which reasons grew after that date | Which addresses changed, and does each old one redirect to its new one? |
| The site feels slow on a phone | The Core Web Vitals report | Which kind of page is slow, and what is the largest thing it loads? |
| A warning appears beside your result, or in the browser | The Security issues report | Has the site been hacked, and what was changed? |
Technical SEO checklist, part one: can Google reach and list the right pages?
This comes first because nothing else counts until it is true. Google's own requirements are that its crawler is not blocked, the page loads successfully and the page has content it can index.
Reach and listing
- Nothing important is blocked from being fetchedRobots.txt is a small file that tells search engines which parts of a site they may fetch. Check that it does not shut out pages you want found, or the style and script files Google needs to read them. See robots.txt vs noindex.
- No page you want found is marked to be left outA noindex tag tells Google not to list a page, and Google then drops it from results entirely. The Page indexing report lists every page where it found one.
- Every important page has a link from another pageGoogle's wording is that every page you care about should have a link from at least one other page on your site.
- Copies of a page point to one preferred versionWhen the same content sits at several addresses, name the main one with a redirect or a canonical tag, a line in the page's code that gives the preferred address. Google treats both as strong signals.
- The sitemap lists only pages you want in searchThat is what Google asks for. XML sitemaps covers the file.
- Filters on a store do not create endless addressesGoogle says its crawlers can spend their time on filter addresses and reach new pages later. What crawl budget is explains when this matters.
Part two: do old addresses and error pages behave?
As a site grows, pages move and pages go. Each should give Google a clear answer. 301 and 302 redirects and the status codes that matter explains the codes below.
Addresses and errors
- Moved pages redirect permanently, straight to the final pageGoogle recommends a permanent redirect set on the server (a 301 or a 308) and then shows the new address in results.
- Removed pages say they are goneA page that is retired with no replacement should return a not found response (404 or 410). Google then removes it from its index, which is what you want.
- A missing page does not pretend to be a real oneIf a nonsense address returns a normal page with an error message on it, Google calls that a soft 404 and reports it.
- The server is not failingServer errors (codes in the 500s) make Google slow its crawling. Google says addresses that keep returning one are removed from its index.
- The site lives at one secure addressThe https version loads and every other version redirects to it. Google prefers https pages when it chooses between copies.
Part three: do pages load quickly and work on phones?
Google judges the phone version of your site and measures speed from real visits, so check both there.
Speed, phones and content
- The three speed measures are in the good rangeGoogle calls them Core Web Vitals. Good means the main content shows within 2.5 seconds, the page reacts to a tap within 200 milliseconds, and the layout shift score is 0.1 or less. What Core Web Vitals are explains each.
- The phone version has everything the desktop version hasGoogle uses the phone version for indexing and ranking, and says it should carry the same content, the same structured data and the same titles.
- The content is in the page Google receivesIn the URL Inspection tool, run Test live URL and open the screenshot. If text you can see in your browser is missing there, the page depends on scripts Google did not run. Headless CMS and SEO goes deeper.
- Schema markup is valid and trueGoogle says markup with required details missing is not eligible for rich results, and that it must be a true representation of the page. See how to add schema markup.
Part four: is the site clean and safe in Google's eyes?
Three quick looks, for problems that are rare and costly.
Penalties, security and languages
- No manual actionA manual action is a penalty applied by a human reviewer at Google. Google says some or all of the site will then not be shown in results. The Manual actions report says whether you have one.
- No security issuesGoogle says a page with a security issue can be shown with a warning label in results, or behind a warning page in the browser. Check the Security issues report.
- Language and country versions point to each otherIf you have them, Google says each version must list itself and all the others. What hreflang is explains the tags.
How do you run a website health check each month?
Five looks in Search Console, in the same order every time. This website health check is the short version of the checklist, for the months between full runs.
A monthly health check
- Page indexing report
Google says the ideal is a count of indexed pages that rises gradually as the site grows. Look for a reason that has jumped since last month. Google says a site under 500 pages probably does not need this report: inspect your main pages one by one.
- Your five most valuable pages
Inspect each one. Confirm that it is on Google and that the address Google chose as the main version is the one you expect.
- Core Web Vitals report
Check whether any group of pages has moved into Poor on mobile.
- Manual actions and Security issues
Both should be empty.
- Sitemaps report
Each sitemap should show Success.
On a site with more than a thousand pages, add the Crawl Stats report, which shows whether Google had trouble reaching your server. Google says smaller sites should not need it. After any release, repeat the first two steps the same day.
What should you fix first?
Whatever stops the most valuable pages from being found. A tool gives every warning the same weight. Your business does not.
| Order | Kind of problem | Example |
|---|---|---|
| First | Anything that keeps important pages out of Google | A noindex tag on service pages, a blocked section, server errors, a security issue |
| Second | Lost or split value on pages that earn money | A moved product page with no redirect, or two copies of a category page competing |
| Third | Slow or broken experience on your busiest kinds of page | Product pages that fail the speed measures on phones |
| Last | Tidy-ups | A missing description on an old article |
Write each fix as a task with four parts: the page or kind of page, what is wrong, what right looks like, and how you will check it. A developer can act on that.
Is this the same as a technical SEO audit checklist?
No. A checklist tells you what is failing. An audit finds out why and what to do first, and it looks at your content and competitors as well as the code. What an SEO audit is explains what one includes. If this list turned up problems whose cause is not clear, that is the point to ask for an SEO audit.
Passing every check makes your pages eligible to be found. Google says that meeting its requirements does not guarantee a page will be indexed, and ranking depends on how useful each page is. Taskcover's Free SEO Audit costs nothing, and the full Technical SEO Audit starts from $2,500 one-time. See the pricing page.
Related serviceTechnical SEO: a fix list your developers can use
We go through your site the way Google does and write every fix as a clear task, most important first.
See the serviceOur services for this
Questions people ask about technical SEO checklists
Do I need paid tools to work through a technical SEO checklist?
Not to start. Google Search Console is a free service, and it covers most of this list: which pages are listed, why others are not, page speed and security warnings. A paid crawling tool earns its cost on larger sites, where nobody can open every page by hand.
Who should own the checklist: marketing or the developer?
Marketing, or whoever answers for enquiries from search, should own the routine, because they notice first when visits fall. The developer owns the fixes. At Taskcover we write each fix as a clear task for your developers and check it once it is live.
Why did a problem we fixed come back?
Usually because the fix was made on one page and the cause sits in a template, a plugin or a setting, so the next update put the problem back. Ask for the cause to be fixed where it starts, and repeat that check after every release.
How long after a fix does Google notice?
Google has to fetch the page again, and it says crawling can take anywhere from a few days to a few weeks. In Search Console you can click Validate fix on an issue in the Page indexing report. Google says validation typically takes up to about two weeks.
Want a second pair of eyes on your site?
Send us your website and we will show you what is stopping your pages from being found, at no cost.
The authors
Who wrote and checked this guide

Written by
Jamiez Nguyen
Founder & CEO
Jamiez Nguyen founded Taskcover and leads strategy and client growth. He started it in 2017 as a team doing search work behind the scenes for other agencies, then opened it to businesses in the USA, Canada and Australia.

Reviewed by
John Edward
CTO
John Edward leads the technical side of Taskcover: how sites are built, how fast they load, and how search engines read them.
Updated Fact-checked About the people at Taskcover
Sources
Where the facts in this guide come from
Facts last checked on October 12, 2026.
- 1Google Search technical requirementsGoogle Search CentralChecked on October 12, 2026
- 2Introduction to robots.txtGoogle Search CentralChecked on October 12, 2026
- 3Block Search indexing with noindexGoogle Search CentralChecked on October 12, 2026
- 4Page indexing reportGoogle Search Console HelpChecked on October 12, 2026
- 5Link best practices for GoogleGoogle Search CentralChecked on October 12, 2026
- 6Understand the JavaScript SEO basicsGoogle Search CentralChecked on October 12, 2026
- 7How to specify a canonical URL with rel="canonical" and other methodsGoogle Search CentralChecked on October 12, 2026
- 8Build and submit a sitemapGoogle Search CentralChecked on October 12, 2026
- 9Managing crawling of faceted navigation URLsGoogle Search CentralChecked on October 12, 2026
- 10Redirects and Google SearchGoogle Search CentralChecked on October 12, 2026
- 11How HTTP status codes affect Google's crawlersGoogle Search CentralChecked on October 12, 2026
- 12Understanding Core Web Vitals and Google search resultsGoogle Search CentralChecked on October 12, 2026
- 13Core Web Vitals reportGoogle Search Console HelpChecked on October 12, 2026
- 14Mobile site and mobile-first indexing best practicesGoogle Search CentralChecked on October 12, 2026
- 15URL Inspection toolGoogle Search Console HelpChecked on October 12, 2026
- 16General structured data guidelinesGoogle Search CentralChecked on October 12, 2026
- 17Manual actions reportGoogle Search Console HelpChecked on October 12, 2026
- 18Security issues reportGoogle Search Console HelpChecked on October 12, 2026
- 19Tell Google about localized versions of your pageGoogle Search CentralChecked on October 12, 2026
- 20Crawl Stats reportGoogle Search Console HelpChecked on October 12, 2026
- 21Sitemaps reportGoogle Search Console HelpChecked on October 12, 2026
- 22About Search ConsoleGoogle Search Console HelpChecked on October 12, 2026
- 23Ask Google to recrawl your URLsGoogle Search CentralChecked on October 12, 2026
