SoftVolt AISoftVolt AI
From the blog

Notes from the people doing the work.

Scoping decisions, build notes and the reporting agencies forward to their clients — written up as the job finishes.

Technical SEO Checklist Agencies Can White Label

A technical SEO checklist agencies can run on any client site: crawlability, speed, indexing and the fixes that actually move rankings.

Published
Updated
Written by
Md Alamgir Hossen
Reading time
8 min read
A man reviewing website data on a laptop at an office desk

A white label technical SEO checklist lets your strategists find the problems while a partner’s developers fix them under your agency’s name. This one covers crawl, indexing, canonicals, sitemaps, Core Web Vitals, structured data and redirects.

Where Google publishes a rule, the item links to it. That way each fix rests on Google’s own documentation, which helps when a client asks why.

How to run a white label technical SEO checklist

Split the work by who does it best. Your team runs the crawl and sets priorities. The partner fixes each item in the CMS or codebase, verifies it and logs it.

For each item, record the check, the rule, the fix and the proof in the ticket. The proof is what goes into the client report.

The checklist at a glance

Area What to check Passes when
Crawl robots.txt, status codes and internal links Important pages can be crawled, and no internal link points at an error
Indexing noindex tags and headers Only pages you want out of Google carry noindex, and none of them is blocked in robots.txt
Canonicals The canonical tag on every template Each page points at its preferred URL, written as an absolute URL
Sitemaps XML sitemap contents and size Only canonical, indexable URLs, with no file over 50,000 URLs or 50MB
Core Web Vitals Field data in Search Console LCP 2.5 seconds or less, INP 200 milliseconds or less, CLS 0.1 or less
Structured data JSON-LD on key templates Valid in the Rich Results Test and true to what the page shows
Redirects Old URLs and redirect chains Permanent server-side redirects go straight to the final URL

1. Crawl

Start with a full crawl of the live site in Screaming Frog or a similar crawler. Then compare the crawl with the XML sitemap.

Sitemap pages that the crawl never reaches are often orphaned, with no internal links. Crawled pages missing from the sitemap may not belong in the index at all.

  • Check robots.txt for rules that block important sections, a common leftover from staging.
  • Look for filters and faceted navigation that create thousands of near-duplicate URLs.
  • List every 4xx and 5xx response, plus the internal links that point at them.
  • Check content that only appears after JavaScript runs, because a crawler may see a thin page.

Keep one rule in mind: robots.txt controls crawling, and it does not reliably keep a page out of Google. The indexing step explains why.

2. Indexing

To keep a page out of Google, use noindex, set as a robots meta tag or an X-Robots-Tag HTTP header. Google’s page on blocking indexing with noindex sets two rules that audits often find broken.

  • The page must not be blocked in robots.txt. If Googlebot cannot crawl it, Googlebot never sees the noindex, and the URL can still appear in results when other pages link to it.
  • Google does not support a noindex rule inside robots.txt itself.

Then check the opposite problem: pages that should rank but carry noindex. A staging setting that survived launch is the usual culprit. Check the CMS’s site-wide indexing setting and the SEO plugin’s rules for each template.

After a fix, Googlebot has to recrawl the page to see the change. Google notes this can take months for less important pages, and the URL Inspection tool can request a recrawl.

3. Canonicals

A canonical tells Google which URL you prefer when several URLs show the same content. Google’s guide to specifying a canonical URL ranks the signals. Redirects and the canonical link tag are strong signals, while sitemap inclusion is a weak one.

  • Use absolute URLs in the canonical tag, not relative paths.
  • Link internally to the canonical URL, not to a duplicate.
  • Do not use robots.txt to choose a canonical.
  • Do not use noindex to stop Google picking a page as canonical within one site.

Typical faults include canonicals that point at a staging domain or at the wrong URL version, such as http instead of https. A crawl that compares each page’s canonical with its own URL catches both.

4. XML sitemaps

A sitemap tells Google which URLs you want in search results. Google’s guide to building and submitting a sitemap sets firm limits and a few rules that agencies often miss.

  • One sitemap can hold up to 50,000 URLs or 50MB uncompressed. Split anything larger into several files.
  • Use fully qualified, absolute URLs.
  • Include the URLs you want to see in search results. In practice, leave out redirects, noindexed pages and errors.
  • Google ignores the priority and changefreq values, so do not spend time tuning them.
  • Google uses lastmod only when it is consistently accurate. It should change with a significant update, not with a new copyright year.
  • Submit the sitemap in Search Console, or add a Sitemap line to robots.txt.

On headless and Next.js builds, generate the sitemap from the real routes. A hand-maintained sitemap drifts away from the site as pages change.

5. Core Web Vitals

Core Web Vitals measure loading, responsiveness and visual stability for real visitors. The Search Console Core Web Vitals report uses these thresholds.

Metric Good Needs improvement Poor
LCP (Largest Contentful Paint) 2.5 seconds or less 4 seconds or less Over 4 seconds
INP (Interaction to Next Paint) 200 milliseconds or less 500 milliseconds or less Over 500 milliseconds
CLS (Cumulative Layout Shift) 0.1 or less 0.25 or less Over 0.25

The report uses real-user data from the Chrome UX Report, covering the last 28 days. Each group of similar URLs takes the status of its worst metric, measured at the 75th percentile of visits.

Once you start validation on an issue, Search Console watches for 28 days before it marks the issue fixed. Tell the client that up front, so nobody expects a green report the day after release.

Typical fixes include image size and loading priority, render-blocking CSS and fonts, heavy JavaScript, third-party scripts and reserved space for banners and embeds. A lab test in PageSpeed Insights confirms a fix on release day. Field data in Search Console is the proof the client will check.

A few template fixes fit inside technical SEO work. A slow site that needs caching, image and script work runs better as a separate Core Web Vitals optimisation project. That project reports before and after field data.

6. Structured data

Structured data describes the page to Google in a standard format. Google’s general structured data guidelines recommend JSON-LD and set these rules.

  • Mark up only content that visitors can see on the page.
  • Make the markup a true representation of the page content.
  • Test it with the Rich Results Test and the URL Inspection tool.

Set the client’s expectations as well. Google does not guarantee that valid markup will appear as a rich result.

A structured data manual action removes a page’s eligibility for rich results, though Google says it does not affect ranking.

On WordPress, schema can come from several plugins at once. Pick one source per template, and validate it again after plugin updates.

7. Redirects

Redirects pass what an old URL earned on to its new address. Google’s guide to site moves with URL changes sets the rules a migration checklist needs.

  • Use permanent server-side redirects, such as 301 or 308, from each old URL to its mapped new URL.
  • Redirect straight to the final destination. If a chain is unavoidable, Google suggests ideally no more than 3 redirects and fewer than 5.
  • Keep redirects in place for at least a year, and consider keeping them indefinitely.
  • Update internal links to the new URLs, and submit the new sitemap in Search Console.

Google also says to expect temporary ranking fluctuation during a move. Tell the client before launch, not after.

Redesigns often leave redirect problems behind, such as merged pages with no redirect or old redirects that now chain into new ones. Our website migration service builds the redirect map from a full crawl, the sitemaps, Search Console and backlink data before launch.

Handing the checklist to a white label partner

Send the audit or ticket list with priorities, and give access to the client’s platform. We ask for the least access that does the job, such as a scoped CMS role and Search Console access. Hosting or repository access comes only when a fix needs it.

Each fix goes to staging first where the platform allows it. We verify it with the tools your team uses: Screaming Frog, Search Console, PageSpeed Insights and schema validators. Then we release it and log it.

The same finding needs a different fix on each platform. On WordPress, a canonical fault may sit in a theme or plugin setting. On a headless Next.js site, it lives in the metadata code.

That is why your partner needs developers on the team as well as SEO specialists.

Before SoftVolt AI, our founder built SEO Agency in Essex, a UK SEO agency’s own site, with technical SEO as the starting point. You can crawl it yourself.

Send us the audit

Our white-label technical SEO service implements the developer tasks in your audit, under your brand. Send the audit or ticket list through our contact page. You will get a written scope and a fixed price within two business days.

Nobody can promise ranking changes. What you will get is every fix verified and logged, ready for your client report.

Comments

No comments yet. Yours would be the first.

Leave a comment

Your email is not published. Comments are read before they appear, so give it a few hours.

Not published.