What is the difference between noindex and robots.txt?

Robots.txt prevents crawling but may still allow indexing if other sites link to the page. Noindex prevents indexing entirely but requires the page to be crawled first. Use robots.txt to block crawling of non-essential resources, and noindex for low-quality pages you don't want in search results.

What are Core Web Vitals and why do they matter for e-commerce?

Core Web Vitals are Google's metrics for user experience: LCP (loading), INP (interactivity), and CLS (visual stability). For e-commerce, poor Core Web Vitals directly correlate with higher bounce rates and lower conversion rates. Google also uses them as a ranking signal.

When should I use a 301 vs 302 redirect?

Use 301 (permanent) redirect when a page has moved permanently and all SEO equity should transfer. Use 302 (temporary) when the move is short-term and you plan to restore the original URL. Use 307 for temporary redirects where the HTTP method must not change (e.g., POST requests).

What structured data types are most important for e-commerce?

The most important schema types for e-commerce are Product (for product pages with price and availability), Review (for ratings), BreadcrumbList (for navigation), FAQ (for Q&A sections), Organization (for brand info), and Video (for product videos). These enable rich results in SERPs.

Technical SEO for E-commerce - Crawling Indexing Speed Structured Data

1

Crawling & Indexing Fundamentals

How Google Crawls E-commerce Sites

Google follows a three-stage process: Crawling (discovering URLs), Indexing (processing and storing page content), and Serving (displaying results). For e-commerce sites with thousands of product pages, effective crawl budget management is critical.

Stage	Description	E-commerce Impact	Optimization
Crawling	Googlebot discovers URLs via sitemaps, internal links, and external backlinks.	Large product catalogs can waste crawl budget on thin or duplicate pages.	Focus crawl budget on high-value product and category pages.
Indexing	Google renders and analyzes page content, storing it in its index.	JavaScript-heavy SPAs may fail to render product content properly.	Use server-side rendering or dynamic rendering for JS-heavy sites.
Serving	Google selects the best result for each query from its index.	Canonical and hreflang tags prevent serving wrong versions.	Set self-referencing canonicals and correct hreflang annotations.

Source: Google's 3-stage crawling and indexing process

Robots.txt Best Practices for E-commerce

Allow product & category pages — never block your core content.
Disallow low-value paths such as /cart/, /checkout/, /account/, /search/, and internal site search results.
Block parameter-heavy URLs like /product?color=red&size=m&sort=price to prevent duplicate crawling.
Reference your sitemap with Sitemap: https://example.com/sitemap.xml.
Test with Google's Robots.txt Tester before deployment.

XML Sitemap Creation & Submission

Structure: Create separate sitemaps for products, categories, brands, and blog posts.
Sitemap index file: Combine all sitemaps under a single sitemap index.
Priority & changefreq: Set higher priority for top-level categories; use changefreq="daily" for active products.
Submission: Submit via Google Search Console, Bing Webmaster Tools, and reference in robots.txt.
Limits: Max 50,000 URLs per sitemap; 50MB uncompressed. Use gzip compression.

Noindex vs Robots.txt vs Canonical — Comparison

Directive	Effect on Crawling	Effect on Indexing	When to Use	Example
robots.txt Disallow	Blocks crawling entirely	URL may still be indexed if linked externally	Block non-essential resources /search, /filter pages	`Disallow: /search?`
Noindex Meta Tag	Page is crawled (must be fetchable)	Prevents indexing entirely	Thin content, out-of-stock products, filtered duplicates	`<meta name="robots" content="noindex">`
Canonical Tag	Page is crawled and indexed	Consolidates ranking signals to preferred URL	Duplicate product variants, paginated series, HTTP vs HTTPS	`<link rel="canonical" href="https://...">`
Noindex + Canonical	Page is crawled	Noindex overrides canonical; page not indexed	When you want to depreciate a page and point to replacement	Use both tags to be explicit
Disallow + Noindex	Crawl blocked; noindex cannot be read	May still be indexed if Google has prior data	AVOID this combination; inconsistent	Not recommended

Comparison of key indexing directives for e-commerce SEO

2

Site Structure & URL Architecture

Flat vs Deep Site Structure

Attribute	Flat Structure	Deep Structure
Definition	All pages within 1–3 clicks from homepage	Pages buried 4+ clicks deep in hierarchy
URL Example	`/shop/running-shoes/nike-air`	`/shop/men/shoes/running/nike/air-max`
Crawl Efficiency	High — Googlebot reaches pages faster	Low — crawl depth wastes budget
User Experience	Fewer taps, faster discovery	More navigation steps, higher bounce risk
Link Equity Distribution	Even distribution across pages	Diluted by hierarchy depth
Best For	Small–medium stores (< 10,000 products)	Enterprise stores with strict categorization
SEO Verdict	Recommended	Use with breadcrumbs

Flat structure is preferred for most e-commerce SEO scenarios

URL Hierarchy Best Practices

Keep it logical and readable: /category/subcategory/product-name.
Use hyphens as word separators (not underscores or spaces).
Aim for 3–5 words in the URL slug; avoid exceeding 60 characters.
Lowercase only. Avoid uppercase, special characters, and query parameters for core pages.
Remove stop words like "a", "an", "the", "and" when not essential.
Include primary keyword naturally in the URL path.

Breadcrumb Navigation Implementation

Schema markup: Implement BreadcrumbList structured data for rich snippet eligibility.
Position: Place breadcrumbs above the page title for user and crawler visibility.
Separator: Use > or / visually; avoid icons that search engines cannot parse.
Hierarchy example: Home > Men's Shoes > Running > Nike Air Max 2025.
Mobile: Breadcrumbs should be tappable and not wrap to multiple lines on small screens.

Pagination Handling

Best practice: Use rel="next" and rel="prev" for paginated series, combined with a View All option when the page count is manageable (< 5,000 products).

Each paginated page should have a self-referencing canonical pointing to itself (not to page 1).
Add rel="next" on page N and rel="prev" on page N+1 to signal pagination.
Include product count and page number in the title tag (e.g., "Running Shoes — Page 2 of 10").
Consider infinite scroll with a "Load More" button instead of traditional pagination for mobile UX.

3

Page Speed Optimization

Core Web Vitals for E-commerce

Google's Core Web Vitals are user-centric metrics that measure loading (LCP), interactivity (INP), and visual stability (CLS). For e-commerce sites, these directly impact conversion rates and organic rankings.

Metric	Full Name	Good	Needs Improvement	Poor	E-commerce Impact
LCP	Largest Contentful Paint	≤ 2.5s	2.5s – 4.0s	> 4.0s	Slow LCP increases bounce rate by 32% on product pages
INP	Interaction to Next Paint	≤ 200ms	200ms – 500ms	> 500ms	Delayed add-to-cart interactions reduce conversion by up to 20%
CLS	Cumulative Layout Shift	≤ 0.1	0.1 – 0.25	> 0.25	Layout shifts cause accidental taps; 15% higher cart abandonment

Core Web Vitals benchmarks for e-commerce (Google thresholds)

≤ 2.5s LCP Good

≤ 200ms INP Good

≤ 0.1 CLS Good

Image Optimization Checklist

Compress images to WebP/AVIF format with 80%+ quality preservation.
Set explicit width and height attributes to prevent CLS.
Use responsive images with srcset for different viewports (320px, 768px, 1024px, 1440px).
Lazy-load below-the-fold product images using loading="lazy".
Implement CDN delivery for product imagery; aim for < 100 KB per product photo.
Use next-gen formats (WebP/AVIF) with fallback JPEG/PNG for legacy browsers.
Serve scaled images — never serve a 4000px image when the display area is 400px.

Caching Strategies

Browser caching: Set Cache-Control headers for static assets (fonts, CSS, JS) to 1 year.
CDN caching: Cache product pages, images, and CSS at edge locations with 24h TTL.
Server-side caching: Use full-page caching for anonymous users; dynamic content for logged-in users.
Object caching: Cache database queries (product listings, category counts) with Redis or Memcached.
Fragment caching: Cache shared components (header, footer, navigation) independently.

Mobile Optimization

Implement AMP for key landing pages (product, category, blog).
Minimize render-blocking resources — inline critical CSS, defer non-critical JavaScript.
Ensure tap targets are at least 48px × 48px per Google's mobile guidelines.
Optimize font delivery — use font-display: swap to prevent invisible text during load.
Reduce server response time (TTFB) to under 800ms on 3G networks.

4

Mobile-First SEO

Google's Mobile-First Indexing

Since July 2024, Google exclusively uses the mobile version of content for indexing and ranking. If your e-commerce site delivers a poor mobile experience, it will rank poorly across all devices.

Key insight: Googlebot uses a mobile Chrome user agent (with a 414px viewport) to crawl and index your site. If mobile content differs from desktop, the mobile version is what gets ranked.

Responsive Design Best Practices

Use a single responsive design rather than separate m.domain URLs.
Set the viewport meta tag: <meta name="viewport" content="width=device-width, initial-scale=1">.
Use CSS media queries for breakpoints at 480px, 768px, and 1024px.
Ensure touch-friendly navigation with adequate spacing and large tap targets.
Test with Google's Mobile-Friendly Test tool and Lighthouse mobile audit.

Mobile UX Elements

UX Element	Best Practice	Common Mistake	SEO Impact
Navigation	Hamburger menu or bottom tab bar with clear labels	Tiny, crowded top navigation bar	High — affects crawlability and user engagement
Search Bar	Prominent, sticky search with autocomplete	Hidden behind an icon	Medium — reduces internal search usage
Product Images	Swipeable gallery with pinch-to-zoom	Static single image with zoom overlay	Medium — affects dwell time and conversion
Add to Cart	Sticky "Add to Cart" button visible at all times	Button below the fold requiring scroll	High — directly impacts conversion rate
Forms	Auto-fill enabled, large input fields, visible labels	Tiny fields, no auto-fill support	Medium — increases form abandonment
Accordion Content	Use accordion for FAQs, specifications, shipping info	Long scrollable text blocks	Low — but improves mobile readability
Page Speed	AMP or optimized mobile-first; LCP < 2.5s	Loading desktop-sized assets on mobile	High — Core Web Vitals ranking factor

Mobile UX best practices and their SEO impact

AMP Implementation Guide

This very page is built with AMP HTML. Key implementation steps for e-commerce:

Start with key templates: Product pages, category landing pages, and blog posts.
Use AMP components: <amp-sidebar> for navigation, <amp-accordion> for specs, <amp-carousel> for product galleries.
Keep CSS under 75KB and inline all styles within <style amp-custom>.
No custom JavaScript — all interactivity uses AMP components and amp-bind.
Validate with AMP Validator or https://validator.ampproject.org/.
Monitor AMP-specific analytics via amp-analytics component.

5

Structured Data for E-commerce

Relevant Schema Types

Schema Type	Properties to Include	Rich Result	Priority
Product	name, image, description, sku, offers (price, priceCurrency, availability), brand, aggregateRating	Product carousel, price badge, star ratings in SERP	Essential
Review	itemReviewed, reviewRating (ratingValue, bestRating), author, reviewBody, datePublished	Star ratings in SERP snippets	High
BreadcrumbList	itemListElement (list of ListItem with position, name, item)	Breadcrumb trail in SERP	High
FAQ	mainEntity (list of Question with name, acceptedAnswer Answer text)	Expandable FAQ in SERP	Medium
Organization	name, url, logo, contactPoint (telephone, contactType), sameAs (social profiles)	Knowledge Panel, Sitelinks Search Box	Medium
Video	name, description, thumbnailUrl, uploadDate, duration, contentUrl, embedUrl	Video thumbnail carousel in SERP	Nice-to-have

Schema.org types ranked by e-commerce SEO impact

Implementation Guide

Preferred format: JSON-LD (as shown on this page). Inline within <script type="application/ld+json">.
Place product schema on every product page. Include price, currency, availability, and brand.
Avoid marking up hidden or user-generated content that isn't visible to all users.
Update dynamically: Ensure price and availability are always current in the schema markup.
Use @id references to link entities (e.g., Product @id referenced by Review itemReviewed).
Include multiple types on the same page using @graph array notation.

Testing & Validation

Google Rich Results Test — validate individual URLs for rich result eligibility.
Schema.org Validator — validate syntax and property correctness.
Google Search Console — monitor structured data errors, warnings, and enhancements in the "Enhancements" section.
Lighthouse SEO audit — includes structured data validation in automated checks.
Common issues: Missing required properties, incorrect property types, mismatched price values.

Pro tip: Google prefers JSON-LD embedded in the page HTML rather than loaded dynamically via JavaScript. Ensure your structured data is present in the initial HTML source, not injected after page load.

6

Site Migration & Redirect Management

301 vs 302 vs 307 — Decision Table

Redirect Code	Name	SEO Equity Transfer	HTTP Method Preserved	Best Use Case
301	Moved Permanently	Full transfer	No (GET for redirected request)	Page permanently moved to new URL; domain migration; HTTP to HTTPS; URL structure change
302	Found (Temporary)	No transfer	No (GET for redirected request)	A/B testing, seasonal landing pages, temporary maintenance, soft launches
307	Temporary Redirect	No transfer	Yes (POST/PUT preserved)	Form submissions, payment redirects, API endpoints where method must not change
308	Permanent Redirect	Full transfer	Yes (POST/PUT preserved)	Permanent changes where HTTP method integrity is critical (rare in e-commerce)

HTTP redirect codes and their SEO implications for e-commerce sites

Site Migration Checklist

Pre-migration: crawl your entire existing site with Screaming Frog or similar tool.
Document all current URLs and their corresponding new URLs in a redirect mapping spreadsheet.
Set up 301 redirects from every old URL to its new equivalent before going live.
Update internal links across the site to point to new URLs.
Generate and submit new XML sitemaps in Google Search Console and Bing Webmaster Tools.
Update robots.txt, canonical tags, and hreflang annotations for the new domain/structure.
Monitor Search Console for crawl errors, 404 spikes, and indexing drops post-migration.
Update all third-party integrations (Google Analytics, Tag Manager, payment gateways, CRMs).
Verify that no redirect chains (301 → 301 → 200) exist; keep redirect depth to a single hop.
Post-migration: monitor rankings and traffic for 4–8 weeks; expect a temporary ranking fluctuation.

Common Migration Mistakes

Mistake	Consequence	Prevention
Not mapping all old URLs	Thousands of 404 errors; massive traffic loss	Run full crawl and use regex to catch dynamic URL patterns
Using 302 instead of 301 for permanent moves	SEO equity does not transfer to new URLs	Audit all redirects with a redirect checker tool before launch
Redirect chains (A → B → C → D)	Diluted link equity and slow page loads	Flatten all redirects to point directly to final destination
No sitemap update post-migration	Google continues crawling old URLs	Submit new sitemap on launch day; remove old sitemap
Changing URL structure without redirects	Complete loss of all indexed page equity	Never change URL structure without 301 mapping
Forgetting to update canonical tags	Google may index old URLs as canonical	Global find-and-replace for canonical references
Migrating during peak sales season	Revenue loss amplifies any SEO dip	Schedule migration during low-traffic periods

Seven most costly site migration mistakes and how to avoid them

SEOzac Tech

Technical SEO for E-commerce

ⓘ Related Resources