Technical SEO & Compliance
Technical SEO & Compliance Architecture: The Complete Website Build-Out Checklist
The store looks fantastic. The product photos are sharp. The checkout works.
Then the awkward questions arrive.
-
Launch Week
Can Google find every product?
Are purchases showing up correctly in Analytics?
Why does sharing a link show the wrong image?
And did that cookie banner actually change what the tracking scripts do?
A website launch involves considerably more than putting a beautiful storefront online.
At Clickative, our approach connects design with the engineering underneath it. For ecommerce, that means planning how the store gets discovered, measures performance, handles information and stays useful as the catalogue changes.
Here’s the checklist we’d bring into that conversation.
01Your Accounts
Get The Keys To Your Own Store
Start with the accounts. Your business should retain control of its domain, hosting, analytics and search properties, with named access for the people helping you manage them.
Google Search Console
Add the website, preferably as a Domain property where appropriate, and verify ownership through DNS.
Google Analytics 4
Create the account or property, add a web data stream and configure the correct currency and reporting time zone.
Google Tag Manager, If Used
Establish a controlled home for approved tracking tags.
Google Merchant Center
Verify and claim the store, complete business details and configure relevant shipping and return settings.
Bing Webmaster Tools
Verify the website and submit its sitemap.
Google Business Profile
If you have physical locations, claim and verify each one, so local searches show accurate hours, contact details and directions.
Search Console’s Domain properties cover protocols and subdomains, making them useful for seeing the wider domain picture.1
When we plan a build, account ownership belongs near the beginning. Access should still make sense long after launch day.
02Measurement
Track The Journey All The Way To The Sale
Knowing that someone visited is useful. Knowing which product they viewed, whether they added it to their basket and whether checkout succeeded is considerably more useful.
Installing an Analytics tag is the starting point. For an ecommerce implementation, the measurement plan can include:
- Product ViewsProduct views and product-list clicks
- BasketAdd-to-cart and remove-from-cart activity
- CheckoutCheckout starts, shipping and payment steps
- PurchaseItems, quantities, revenue and refunds
Plus the key events that matter, such as completed purchases or qualified enquiries
Google’s ecommerce events require the appropriate implementation and parameters. Product identifiers, currency, values and transaction IDs need deliberate handling.2
We would also test duplicate purchase reporting, checkout across different domains and payment-provider referrals. Campaign tags and available referral information should be captured consistently, including identifiable AI referrals, without inventing attribution when the source isn’t available.
Link Search Console to GA4. If advertising is in scope, configure Google Ads conversions without double-counting purchases. Approved tags can be managed by page type, brand or storefront.
Customer names, emails and addresses should stay out of ordinary Analytics events and page URLs.
03Catalogue Structure
Build A Catalogue Google Can Actually Explore
A product shouldn’t need to be discovered through a search box that only a human knows how to use. The browsing structure needs a clear path:
- StorefrontWhere browsing starts.
- CategoryA broad group of products.
- Subcategory Or CollectionA narrower, related set.
- ProductThe page that sells.
Depending on the catalogue, shoppers might also browse by brand, product type or use case. Breadcrumbs help them understand where they are and move between levels.
Our architecture checklist includes:
- Crawlable HTML links to important products and collections.
- Clear headings, useful category descriptions and meaningful URLs.
- Pagination with real links and distinct addresses.
- Deliberate rules for filters, sorting and internal search results.
- Relevant connections between stores or brands when several are involved.
- One version of every address: a single host (https, with or without www), consistent trailing slashes and lowercase paths, with the other versions redirecting.
- Breadcrumb structured data that matches the visible trail.
- Basket, checkout and account pages kept out of search results.
- For several languages or countries,
hreflangannotations linking each page to its other versions.3
Infinite scroll can improve browsing, but it still needs a crawlable route to the products beyond the first screen.4
Otherwise, the back half of your catalogue risks becoming a very well-designed secret.
04Product Pages
Give Every Product A Proper Home
A quick-view panel is convenient. A product also needs a dependable page someone can open directly, bookmark and share.
When we design these experiences, the product’s URL, title, description and structured data need to agree with the actual page. A complete product page should cover:
A Stable Address
A stable, descriptive URL and a considered canonical address.
A Clear Title
A clear product heading and distinctive page title.
The Full Picture
Useful descriptions, specifications, images and variant information.
Price And Availability
Accurate price, currency, availability and purchase options.
Delivery And Returns
Delivery, return and business information customers can find.
Structured Data
Product structured data matching the visible information.
Depending on the product, structured data can include Product, Offer, genuine review information and identifiers such as brand, SKU or GTIN. Product variants may also call for ProductGroup markup, and shipping and return details can be marked up as well (OfferShippingDetails, MerchantReturnPolicy). Eligibility depends on meeting Google’s requirements.5
Important content should be available to crawlers, with server-rendered HTML a strong option. Opening a product from a list should still preserve direct access, sharing and sensible browser-back behaviour.
What Happens When Stock Changes?
Temporarily unavailable products can retain useful pages, with honest stock information and relevant alternatives. For discontinued products, the plan might be to:
Keep A Useful Page
A genuinely useful information page stays.
Redirect To A Replacement
A close replacement takes over the address.
Return A 404 Or 410
A proper
404or410when the page is removed.
Automatically sending every unavailable product to an unrelated search page is a poor substitute for that decision.
05Landing Pages
Turn Your Catalogue Into Thousands Of Search-Focused Pages
Our automated landing-page system can generate thousands of SEO-optimised pages by combining individual product names or broader product categories with the cities and states your business serves.
- Product + City
- Product + State
- Category + City
- Category + State
Each page brings together relevant products, a descriptive URL, tailored headings and introductory content, giving shoppers a useful starting point for exploring what you offer in their area. We build the publishing rules around:
- Enough relevant products and useful information to justify each page.
- A unique address, title, heading and introduction.
- Accurate product counts and current catalogue information.
- Links from the appropriate browsing directories.
- Editorial controls to edit, lock, preview or retire content.
AI-assisted introductions can support production, with prompts, model choices and review controls managed in the dashboard. Approved copy should remain stable until there’s a reason to update it. An admin view can filter collections, show generation history and export URL inventories for review.
A minimum product count is one screening rule. It doesn’t, by itself, make a page valuable.
Location pages should reflect genuine product availability, delivery coverage, stores or local offers, with useful information for the shopper.
06The Blog
Make The Blog Part Of The Store
A buying guide should help someone make a decision and find the relevant products.
Our content checklist connects the editorial side with the catalogue:
- Permanent article URLs and crawlable category archives.
- Individual summaries, visible publication dates and appropriate author details.
- Accurate
Articlestructured data. - Relevant product links or sliders within the content.
- Related articles and logical next steps.
- Responsive images with useful alternative text.
An AI-assisted editorial system can support topic queues, duplicate-topic checks, scheduled publishing, image briefs and missing-content checks. Review and approval should reflect the risk and subject matter.
The useful goal is a library worth reading. Publishing on a schedule doesn’t make repetitive or unhelpful content useful to shoppers.
07Discovery
Set Up Discovery, Without The “Instant Indexing” Fantasy
Search engines need accurate routes into the catalogue and signals when it changes.
| Tool | Its Job |
|---|---|
| XML sitemaps | List canonical, indexable products, collections and published articles |
robots.txt |
Guide crawling and identify the sitemap location |
| Search Console | Monitor discovery, indexing and search performance |
| Merchant Center feed or API | Submit and maintain product information |
| IndexNow | Notify participating search engines about changed URLs |
Sitemaps should reflect real changes, use accurate lastmod dates and be split as the catalogue grows. Submissions and errors should be logged.6
Google’s Indexing API is restricted to eligible job-posting and livestream pages. It doesn’t support ordinary ecommerce product pages. Rotating accounts or keys to evade quotas is also contrary to Google’s guidance.7
IndexNow supports participating engines and batches of up to 10,000 URLs; acceptance acknowledges a notification, not an indexing outcome.8
- PublishThe page goes live.
- DiscoverA search engine learns it exists.
- CrawlIt fetches the page.
- IndexIt may store the page.
- RankIt may show it for a search.
Publishing, discovering, crawling, indexing and ranking are separate steps. A submission receipt isn’t a search result.
robots.txt can also set rules for individual AI crawlers. Google-Extended, one of its tokens, decides whether Google may use the content to train and ground its Gemini models, without affecting Google Search. Whichever way you go, it’s worth deciding on purpose.9
08Link Previews
Make Shared Links Look Like Your Brand
A customer shares a product in WhatsApp. The preview should make sense.
This is the one I was telling you about!
Set up Open Graph and social-card metadata with the right title, description, image and canonical sharing URL for each page type.
Product cards can use catalogue photography or generated branded layouts. They should be refreshed when the details they display change. Articles and collections need suitable previews too, with sensible defaults if an image is missing.
Search results can carry your brand as well: Organization structured data (name, logo and contact details) and a site name and favicon help Google present the store the way you would introduce it.
Optional share buttons can support email, messaging and social platforms.
It’s a small detail that becomes very visible when someone recommends your product.
09Mobile Speed
Treat Mobile Speed As Part Of Shopping
A fast homepage doesn’t tell you whether a busy product page or checkout performs well.
Our performance checklist includes responsive layouts, appropriately sized WebP or AVIF images, caching and selective script loading. Below-the-fold images can load lazily; the main product or hero image usually needs prompt loading.
Reserve image space, keep critical styling available early and defer suitable nonessential scripts. Monitor Core Web Vitals and test on realistic mobile connections.
Nobody should have to watch your entire tracking stack assemble itself before choosing a shoe size.
10Privacy & Compliance
Make Privacy And Compliance Work In The Product
The cookie banner and privacy policy need to match what the website actually does.
Agree the applicable requirements for the markets served, then connect them to implementation:
- Privacy information, cookie disclosures and relevant user controls.
- Consent or opt-out behaviour appropriate to each technology and jurisdiction.
- Shipping, returns, terms, contact and business details.
- Data collection, retention and deletion processes.
- Provider access and appropriate handling of customer information.
Where consent is required, test the behaviour of tags before and after acceptance, rejection and withdrawal:
- Before A ChoiceWhat runs before anyone chooses?
- AcceptedWhat starts after acceptance?
- RejectedWhat stays off after rejection?
- WithdrawnWhat stops after withdrawal?
Google Consent Mode adjusts Google-tag behaviour; it doesn’t provide the consent interface itself or establish legal compliance.10
Accessibility also belongs here: keyboard use, visible focus, contrast, labelled forms, readable errors and descriptive image text. WCAG provides a useful framework, with the required scope agreed for the project.11
11Security
Protect The Store Behind The Storefront
HTTPS is one part of the security plan.
Administrative permissions, stronger sign-in, protected API keys, software updates, backups and recovery testing matter too. Payment integration should minimise direct handling of card information and have its responsibilities agreed with the provider.
Staging sites should be protected, excluded from live submissions and kept separate from production measurement. Private customer information needs access controls.
The domain that sends order confirmations needs authenticating as well, with SPF, DKIM and DMARC, so receipts reach inboxes and the domain is harder to spoof.12
And
robots.txtis not a privacy barrier. A crawler blocked from a page also can’t read itsnoindexinstruction.13
Before launch, check that the production store hasn’t inherited the staging site’s search restrictions.
12Launch Rehearsal
Run A Real Launch Rehearsal
Before calling the build ready, walk through the entire journey:
-
Find A Product
Find a product through browsing and search.
-
Buy It
Select variants, add it to the basket and complete a test purchase.
-
Check The Order
Check stock, totals, confirmation emails and refund handling.
-
Check The Measurement
Validate Analytics events, consent behaviour and duplicate-order reporting.
-
Check The Search Details
Test structured data, canonical URLs, redirects and mobile navigation.
-
Check What Runs Behind It
Check sitemaps, permissions, error pages and monitoring.
Replacing An Existing Store?
Crawl the old site first and map every address that has traffic, links or rankings to its new home with a permanent (301) redirect. Keep those redirects in place, submit the new sitemap and watch Search Console for errors after the switch.14
In our Imagine, Design, Build and Refine process, these decisions run from planning through testing. After launch, dashboards can surface feed errors, failed automations and indexing issues. Scheduled jobs should process genuine changes, respect API limits, log failures and offer pause controls.
A complete build-out makes the store easier to find, understand, buy from and maintain.
Plan Your Store’s Complete Build-Out
From the first account to the launch rehearsal, we plan the details that help a store get found, measured and trusted.
Tell us what you’re building.
We’ll put together a FREE concept proposal with visual directions and functional ideas before you commit.
References
- Google: Add a property to Search Console
- Google Analytics: Measure ecommerce
- Google: Tell Google about localized versions of your page
- Google: Pagination and incremental page loading
- Google: Merchant listing structured data and product variants
- Google: Build and submit a sitemap
- Google: Indexing API quickstart
- IndexNow documentation
- Google: Google’s common crawlers (Google-Extended)
- Google: Consent mode overview and ICO: Storage and access technologies
- W3C: Web Content Accessibility Guidelines 2.2
- Gmail: Email sender guidelines
- Google: Robots.txt introduction
- Google: Site moves with URL changes