Launch checklist
What to check before you launch an affiliate site, a SaaS app or any website. Every Google rule links to Google's own documentation; the rest is practical advice. Press Copy as prompt and paste a list into a ContentForger build or change request.
By Thomas Lovas Lokoy · Sources checked 12 November 2026 · Not legal advice
Affiliate site
Content sites that earn a commission when a reader buys or signs up through a link.
A unique, descriptive title on every page
Google's guidance: write descriptive and concise text for each page's <title>, brand it concisely, and do not repeat the same words over and over. Every page gets its own title.
A meta description that summarises the page
A short, relevant summary of what the page is about. Google may show it as the snippet when it describes the page better than the page text, so it is not guaranteed to appear — write it anyway, one per page.
Search Console verified, sitemap submitted
Verify the domain in Search Console, then submit the sitemap in the Sitemaps report. One sitemap file holds at most 50,000 URLs or 50 MB uncompressed. Google only uses <lastmod> when it is consistently accurate, so set it to the real date of the last significant change, not the build time.
robots.txt for crawling, noindex for hiding
robots.txt manages crawling; Google says it is not a mechanism for keeping a page out of Google. To keep a page out of results use noindex — and do not also block that page in robots.txt, or the crawler never sees the noindex.
One canonical URL per page
Add rel="canonical" pointing at the preferred URL, so variants (tracking parameters, trailing slashes, http/https) consolidate to one page.
Affiliate links marked rel="sponsored"
Google asks you to mark paid and affiliate links with rel="sponsored" (rel="nofollow" is also accepted). Its spam policies say such links are not a violation when they are qualified this way.
A clear affiliate disclosure
Tell readers you may earn a commission, near the links and on a disclosure page. In many countries this is a legal requirement (in the US, the FTC's Endorsement Guides); check the rules for the countries your readers are in.
More than a copy of the merchant's page
Google's spam policies name "thin affiliation": pages that copy product descriptions and reviews from the merchant without adding value. Add your own testing, comparisons, photos and honest downsides.
Sub-ID tracking on every link
Most networks let you add a sub-ID to the tracking link (each network names the parameter differently — use the one its link builder shows). Use one value per page or placement, e.g. "home-hero" or "best-vpn-table", so the network report shows which page earned. Click one link yourself and confirm it appears in the report.
Know the payout model: CPA, CPS, revshare
CPA (cost per action) pays a fixed amount when the visitor completes the action the advertiser defines, such as a sign-up or first deposit. CPS (cost per sale) pays a percentage of the sale value. Revenue share pays a percentage of what the customer brings the advertiser over a period, sometimes for the customer's lifetime. Some programmes mix them. Before you promote an offer, read its terms: the qualifying action, cookie window, allowed countries and traffic sources, and when commissions can be reversed.
Structured data basics: Organization + BreadcrumbList
Start with Organization on the home page and BreadcrumbList on inner pages, as JSON-LD. Follow the general guidelines (mark up only what is visible on the page) and check it in the Rich Results Test. Google does not guarantee rich results even for correct markup.
No review stars for your own business
Google limits review snippets for Organization and LocalBusiness to sites that review other businesses (its "self-serving reviews" rule). Show real customer reviews on the page if you have them, but do not add Review/AggregateRating markup about yourself — and never publish invented reviews.
Core Web Vitals in the green
Google's "good" thresholds, measured at the 75th percentile of page loads: LCP within 2.5 seconds, INP of 200 milliseconds or less, CLS of 0.1 or less. Check real-user data in Search Console and lab data in PageSpeed Insights; one lab run varies, so test more than once.
Analytics with consent
Install analytics (for example Google Analytics 4) and decide the few events that matter (sign-up, purchase, outbound click). Where consent is required, set a default consent state and update it from your cookie banner — Google's consent mode documents how.
Legal pages: privacy, terms, contact
A privacy policy that says what data you collect and why, terms of use, and a way to contact you. If you have visitors in the EU, the GDPR applies to their personal data, including analytics cookies. Requirements differ by country — get advice for yours.
SaaS site
Apps people sign up for and pay to use.
A unique, descriptive title on every page
Google's guidance: write descriptive and concise text for each page's <title>, brand it concisely, and do not repeat the same words over and over. Every page gets its own title.
A meta description that summarises the page
A short, relevant summary of what the page is about. Google may show it as the snippet when it describes the page better than the page text, so it is not guaranteed to appear — write it anyway, one per page.
Search Console verified, sitemap submitted
Verify the domain in Search Console, then submit the sitemap in the Sitemaps report. One sitemap file holds at most 50,000 URLs or 50 MB uncompressed. Google only uses <lastmod> when it is consistently accurate, so set it to the real date of the last significant change, not the build time.
A pricing page that matches checkout
Show the price, the billing period, the currency and whether tax is included, what each plan includes, and how to cancel. The price on the page must be the price at checkout.
Onboarding to a first result
Get a new user from sign-up to one useful result in as few steps as you can: sensible defaults, an example to start from, and empty states that say what to do next. Measure how many sign-ups reach that first result.
Transactional email that arrives
Send sign-up confirmations, password resets and receipts from your own domain with SPF and DKIM set up, and add DMARC. Google's sender guidelines require all three from anyone sending more than 5,000 messages a day to Gmail accounts. Keep marketing email separate and give it an unsubscribe link.
Error tracking and alerts
Capture server and browser errors with a tool such as Sentry, tag each release, and alert on new errors. Never log passwords, tokens or full card data.
Security basics
Keep keys in environment variables, never in the code. Check on the server that the signed-in user owns every row they read or change (Row Level Security in Supabase). Rate-limit sign-in, sign-up and anything that costs you money per request.
Structured data basics: Organization + BreadcrumbList
Start with Organization on the home page and BreadcrumbList on inner pages, as JSON-LD. Follow the general guidelines (mark up only what is visible on the page) and check it in the Rich Results Test. Google does not guarantee rich results even for correct markup.
No review stars for your own business
Google limits review snippets for Organization and LocalBusiness to sites that review other businesses (its "self-serving reviews" rule). Show real customer reviews on the page if you have them, but do not add Review/AggregateRating markup about yourself — and never publish invented reviews.
Core Web Vitals in the green
Google's "good" thresholds, measured at the 75th percentile of page loads: LCP within 2.5 seconds, INP of 200 milliseconds or less, CLS of 0.1 or less. Check real-user data in Search Console and lab data in PageSpeed Insights; one lab run varies, so test more than once.
Analytics with consent
Install analytics (for example Google Analytics 4) and decide the few events that matter (sign-up, purchase, outbound click). Where consent is required, set a default consent state and update it from your cookie banner — Google's consent mode documents how.
Legal pages: privacy, terms, contact
A privacy policy that says what data you collect and why, terms of use, and a way to contact you. If you have visitors in the EU, the GDPR applies to their personal data, including analytics cookies. Requirements differ by country — get advice for yours. If business customers send you their customers' personal data, they may ask for a data processing agreement.
Any website
The basics every site should have before launch.
A unique, descriptive title on every page
Google's guidance: write descriptive and concise text for each page's <title>, brand it concisely, and do not repeat the same words over and over. Every page gets its own title.
A meta description that summarises the page
A short, relevant summary of what the page is about. Google may show it as the snippet when it describes the page better than the page text, so it is not guaranteed to appear — write it anyway, one per page.
Search Console verified, sitemap submitted
Verify the domain in Search Console, then submit the sitemap in the Sitemaps report. One sitemap file holds at most 50,000 URLs or 50 MB uncompressed. Google only uses <lastmod> when it is consistently accurate, so set it to the real date of the last significant change, not the build time.
robots.txt for crawling, noindex for hiding
robots.txt manages crawling; Google says it is not a mechanism for keeping a page out of Google. To keep a page out of results use noindex — and do not also block that page in robots.txt, or the crawler never sees the noindex.
One canonical URL per page
Add rel="canonical" pointing at the preferred URL, so variants (tracking parameters, trailing slashes, http/https) consolidate to one page.
HTTPS, a real 404 page and working redirects
Serve every page over HTTPS, return a 404 status for pages that do not exist (not a 200 with an error message), and redirect old URLs to their new home with a 301.
People-first content: who, how and why
Google suggests evaluating content by "Who, How, and Why": who made it (a byline and about page), how it was made (your testing or sources), and why it exists (to help readers, not only to rank).
Images with descriptive alt text and file names
Google uses alt text, captions and the surrounding page to understand an image. Describe what the image shows; size images for the slot they fill.
Structured data basics: Organization + BreadcrumbList
Start with Organization on the home page and BreadcrumbList on inner pages, as JSON-LD. Follow the general guidelines (mark up only what is visible on the page) and check it in the Rich Results Test. Google does not guarantee rich results even for correct markup.
Core Web Vitals in the green
Google's "good" thresholds, measured at the 75th percentile of page loads: LCP within 2.5 seconds, INP of 200 milliseconds or less, CLS of 0.1 or less. Check real-user data in Search Console and lab data in PageSpeed Insights; one lab run varies, so test more than once.
Analytics with consent
Install analytics (for example Google Analytics 4) and decide the few events that matter (sign-up, purchase, outbound click). Where consent is required, set a default consent state and update it from your cookie banner — Google's consent mode documents how.
Legal pages: privacy, terms, contact
A privacy policy that says what data you collect and why, terms of use, and a way to contact you. If you have visitors in the EU, the GDPR applies to their personal data, including analytics cookies. Requirements differ by country — get advice for yours.