Technical SEO has a reputation problem. It sounds like server room work, but it is really a set of answerable questions: can Google find your pages, can it read them, do they load fast enough for a phone on mobile data, and does anything confuse the crawler? Get these wrong and even great content underperforms. Get them right and every future article you publish starts from a stronger position.
Crawl and index: can Google reach your pages
Start in Google Search Console. Check the Pages report for what is indexed and, more importantly, what is excluded and why. A few common culprits: accidental noindex tags left over from development, a robots.txt that blocks more than it should, and orphan pages that no internal link points to. Then look at your sitemap: it should list your real, indexable pages, load fast, and stay under the practical limits. Finally, review the site architecture itself. Important pages should be reachable within a few clicks from the homepage, and your internal links should use descriptive anchor text that tells both users and crawlers what the target page is about.
One habit pays for itself: whenever you publish or move a page, check that the old URL situation is handled. Redirects should be 301s to the closest matching page, not to the homepage. Redirect chains, where URL A points to B which points to C, slow crawlers and leak authority. Keep chains to one hop.
Speed, mobile, and rendering
Speed is a ranking factor and a conversion factor, and on mobile data it is brutal. Test your key pages with PageSpeed Insights and look at the real user data, not just the lab score: Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. The usual fixes are unglamorous: compress images to modern formats, defer scripts that block rendering, and stop loading five analytics tags you never open. Every second matters more on product and service pages than on blog posts, because that is where money changes hands.
Mobile deserves its own pass because Google indexes mobile first. Tap targets should be finger sized, text readable without pinching, and no content hidden behind elements that only work with a mouse. Check that your structured data, headings, and key content exist in the mobile version too; if your mobile theme strips out the schema or the FAQ section that the desktop page has, the crawler never sees them.
| Area | Check | Why it matters |
|---|---|---|
| Crawl | robots.txt, sitemap, internal links, no orphan pages | If crawlers cannot reach a page, it cannot rank |
| Index | No accidental noindex, canonicals correct, duplicates resolved | Wrong signals split or hide your rankings |
| Speed | Core Web Vitals on real user data, image compression, deferred scripts | Slow pages rank worse and convert worse |
| Mobile | Tap targets, readable text, same content and schema as desktop | Google indexes your mobile version first |
| Schema | Valid structured data on eligible pages, no errors in Rich Results test | Eligibility for rich results and clearer entity understanding |
| Security | HTTPS everywhere, no mixed content, valid certificates | Trust signal for users and a confirmed lightweight ranking factor |
| Redirects | 301s to closest match, single hop chains, no redirect loops | Preserves authority when URLs change |
The five layer audit sequence
Sitemap, robots, internal links. Nothing else matters if pages are unreachable.
Noindex leftovers, canonical tags, duplicate clusters cleaned up.
Real user Core Web Vitals on your money pages, mobile first check.
Valid structured data, HTTPS everywhere, no mixed content.
Single hop 301s, no loops, quarterly re check on autopilot.
Structured data and the ongoing routine
Schema markup does not guarantee rich results, but it makes your pages eligible and helps search engines understand what they are: a local business, a product with a price, an article with an author, an FAQ with real questions. Validate with the Rich Results test after every template change, because themes and plugins break schema silently. Keep it honest: mark up only content that is visible on the page.
Finally, treat this checklist as a routine, not a project. Technical SEO decays: plugins update, content teams publish duplicate pages, someone "temporarily" noindexes a section. A quarterly pass through Search Console, a speed check on your top pages, and a crawl of new URLs keeps small issues from becoming ranking problems. If you would rather have someone else run it, our SEO services start every engagement with exactly this audit.
A practical technical SEO release checklist
Run this pass before a new template, migration, campaign page, or major content update goes live. The aim is not to predict a ranking result. It is to confirm that the page is reachable, understandable, usable, and measurable when real visitors and crawlers arrive.
Before release, test the paths
- Start from a clean browser session and follow links from the homepage, navigation, category pages, and related content. Confirm that the intended page can be reached without relying on a search box or a private login.
- Crawl the release candidate and inspect status codes, blocked resources, broken internal links, and pages that are only reachable through a redirect. Compare the discovered URLs with the approved launch list.
- View the source of each important page and confirm that the canonical points to the preferred final URL. Check that alternate versions such as trailing slash, uppercase, parameter, and secure variants resolve consistently.
- For every replaced URL, test the old address directly. It should return one relevant 301 response to the final destination. Check that there are no loops, chains, soft error pages, or redirects that send a visitor to an unrelated homepage.
Review what people receive
- Use a narrow mobile viewport and a real touch device when possible. Check navigation, menus, forms, accordions, tables, and consent controls. Important text, links, headings, and structured data should remain available in the mobile experience.
- Inspect every large image at its rendered size. Serve an appropriately sized source, preserve its aspect ratio, and reserve space so the page does not jump while the image loads. Use meaningful alternative text for informative images and empty alternative text for decorative ones.
- Run a keyboard only pass. The focus order should follow the content, focused links should be visible, and controls should have names that make sense when read by assistive technology. Do not make colour the only way to communicate an error or state.
- Check headings, page title, language, link labels, and contrast in the final template. Accessibility improvements help people use the page and often expose structural problems that a crawler report will not show.
Make the review repeatable after launch
Assign measurement
Name one owner for Search Console inspection, analytics checks, and the release record. Confirm that the page view event, form or purchase event, consent behavior, and campaign parameters work as intended. Record the expected URL and event names before launch so a missing signal is easy to spot.
Spot check the live page
After release, open the public URL from a logged out browser and from a phone. Test the canonical, robots directive, key links, images, primary action, and any important form. Submit the new URL for inspection when appropriate, but treat the inspection result as a diagnostic rather than a promise.
Keep a short record
Save the crawl date, changed URLs, redirect map, owner, and unresolved issues. Recheck a sample of old URLs and new pages after the first content or template update. A small record makes it easier to tell a genuine release issue from a later change.