We fix the faceted navigation that’s generating thousands of duplicate URLs from your filters, the category pages that are just product grids with no content Google can rank, the product variants competing with each other instead of consolidating authority, and the structured data gaps keeping your products out of Google Shopping and AI answers. We measure success in organic revenue — not rankings reports.
BigCommerce is one of the strongest ecommerce platforms for SEO out of the box — automatic sitemaps, canonical tags, clean hierarchical URLs, CDN delivery, SSL, and native Product schema. But “strong out of the box” and “actually ranking and converting” are two different things.
Every time a customer filters by size, color, price, brand, or material on your category pages, BigCommerce generates a unique URL for that combination. A store with 20 categories and 8 filter options can generate 40,000+ indexable parameter URLs from a few hundred real pages. BigCommerce canonicalizes filtered URLs back to the base category by default — but it doesn’t stop Google from crawling them. Your crawl budget gets spent on filter permutations instead of your actual revenue pages.
The fix isn’t “noindex everything” — it’s selective. Some filter combinations have real search demand (“red leather handbags” is a query people search; “handbags sorted by price ascending” is not). We identify which filter combinations earn indexation based on actual search demand and block the rest.
BigCommerce category pages ship with a product grid, a category name as an H1, and nothing else. Your category pages rank for buying queries — “pecan gift boxes,” “leather laptop bags,” “organic protein powder” — high-volume, high-intent searches where the buyer has decided to purchase and is choosing where. If your category page is just a grid, your competitor with editorial buying guidance above the grid outranks you.
We integrate concise editorial content into your category templates — positioned above the product grid without pushing products below the fold. Google gets something to rank. Your shoppers get context that increases add-to-cart rate.
Product options — size, color, material, weight — can create separate indexable URLs on BigCommerce. Without deliberate canonical strategy, your 5-lb bag of pecans competes with your 3-lb bag, your 1-lb bag, and the parent product page. Google indexes all of them. Your ranking authority splits four ways.
The decision isn’t automatic — it’s per-product. Some variants genuinely deserve separate indexation (a “red leather handbag” is a different search query from a “black leather handbag” and people search both). Others should consolidate to the parent (nobody searches “pecan halves 3-lb bag” as a separate query from “pecan halves”). We audit every variant URL against actual search demand and set canonicals accordingly.
Every BigCommerce product exists in three places simultaneously: the visible page (what the customer sees), the structured data in the HTML (what Google’s crawler reads), and the Google Merchant Center feed (what Google Shopping uses).
When the price on your page says $84.95, the Product/Offer schema says $79.95 (last sale price cached in the template), and the Merchant Center feed says $89.95 (pre-discount list price from the CSV export) — Google flags the mismatch. Your rich results disappear from search. Your Shopping listings get demoted. Your products stop appearing in AI shopping answers from ChatGPT Shopping and Google AI Overviews.
We audit all three layers and fix the inconsistencies that are silently costing you revenue every day you don’t know about them.
Stencil — BigCommerce’s Handlebars-based theme engine — renders server-side by default, which is good for SEO. But the theme makes decisions about your heading hierarchy, canonical tags, schema output, and image loading that most store owners have never inspected. Any customization — adding a section, changing a layout, installing an app — can introduce heading violations, schema conflicts, or lazy-loading that hides content from Google.
If you’re on Catalyst — BigCommerce’s newer Next.js headless framework — the stakes are higher. Catalyst can render server-side, but client-side rendering gaps are easy to introduce. AI crawlers don’t execute JavaScript at all, so anything rendered only client-side is invisible to ChatGPT, Perplexity, and Google’s AI Overviews.
ChatGPT Shopping, Google AI Overviews, Perplexity Shopping, Amazon Rufus — these AI engines are becoming a real product discovery channel in 2026. They cite product information from stores that have three things: clean structured data, server-rendered content, and consistent entity information.
BigCommerce has a structural advantage here: Stencil renders server-side, and the platform generates Product/Offer schema automatically. But “has the advantage” and “is using the advantage” are different things. Most BigCommerce stores have incomplete schema (missing Review, FAQ, Organization, BreadcrumbList), inconsistent entity data (the brand name rendered three different ways across the site), and no strategy for getting products cited in AI answers.
This is early-mover territory — most of your competitors haven’t started.
This is not a menu of options. It’s the full scope of what a BigCommerce SEO engagement covers — organized by what part of your store we’re working on, so you can see exactly where your money goes. Everything below is delivered in-house. Nothing is subcontracted. Nothing is aspirational.
Category pages rank for buying queries — the high-volume, high-intent searches where someone has decided to buy and is choosing where. This is where most of your organic revenue will come from.
Product pages convert. They rank for specific product queries and long-tail buying terms. On BigCommerce, they also carry your structured data — the information Google uses for rich results, Shopping, and AI answers.
Nothing above works if the technical layer is broken. This is the infrastructure work.
AI engines — ChatGPT Shopping, Google AI Overviews, Perplexity Shopping, Gemini, Amazon Rufus — are becoming a real product discovery channel. Getting your products cited in AI answers is now a distinct visibility goal alongside traditional search rankings.
BigCommerce has a genuine advantage here: Stencil renders server-side by default, meaning AI crawlers can actually read your product pages. We build on that advantage:
We report so you can measure ROI, not so we can show you a chart that goes up. Every month you get a report written in plain language covering what we did, what changed, and what’s next. But the metrics that matter for an ecommerce store aren’t rankings and impressions — they’re organic revenue, organic transactions by category, add-to-cart rate from organic traffic, and cost of acquisition compared to your paid channels. We track all of these in GA4 and report them alongside the SEO work that drove them, so you can see the connection between what we did in month 2 and what your revenue looked like in month 4.
On the Growth plan, you get a monthly strategy call with your SEO lead plus Slack access for real-time questions between reports. Because if you’re running a flash sale next Tuesday, waiting until the monthly report to discuss SEO implications is too late.
Drupal sites aren’t comparable. A 50-page brochure site and a 15,000-page multilingual multisite are different projects, and pricing that pretends otherwise won’t survive contact with your actual site. Start with the free audit — it tells us both exactly what your site needs.
A complete technical and content audit of your Drupal site, using the same rendered-output methodology we run on paid engagements — free, because we’d rather show you the work than describe it.
Ongoing Drupal SEO for sites on Drupal 10 or 11 that need continuous technical optimization, content work, deployment QA, and steady authority building.
Technical work every month
Content & AI search
For projects that don’t fit a standard retainer: migrations, complex upgrades, multisite, headless, or ongoing white-label delivery for agencies.
Prices are transparent starting points. Actual scope is confirmed after the free audit or a discovery call — because pricing that survives contact with your Drupal site is more useful than pricing that looks clean on a page.
What we did: A six-month engagement in three phases: technical cleanup prioritized by impact, then content-model restructuring for the vocabularies we promoted into real landing pages, then ongoing optimization and deployment QA. We consolidated the indexable surface from 11,400 to 3,800. Rebuilt twelve taxonomy vocabularies as proper landing pages with curated Views displays and unique content. Fixed 2,200 redirect chains in one coordinated deployment. Rebuilt Multilingual Associations across all three languages and revalidated hreflang against rendered output. Implemented Config Split to isolate environment-specific SEO settings, and added a fifteen-item SEO QA checklist to the release process. Implemented Schema.org Metatag for EducationalOrganization, Course, Event, and Article types — which also made the department pages far more extractable for Google AI Overviews, increasingly where prospective students start their research.
Indexed URL bloat
Organic dept traffic
Inquiry submissions
Ranking loss
Results reflect a real engagement over approximately eight months. The numbers are accurate for this project. We don’t guarantee the same outcomes elsewhere — search depends on your market, competition, content, and starting point. What we guarantee is the methodology.
Want the full breakdown? The complete case study — the technical audit findings, the exact Config Split structure we built, the URL restructuring plan, and the month-by-month recovery curve — is available on request. We share it after a short conversation to confirm you’re a fit (we don’t send full engagement details to competitors).
Yes — in some ways Drupal is stronger for SEO than any competing CMS. Its content model gives granular control over how content is structured, classified, and rendered. Core modules — Metatag, Pathauto, Redirect, Simple XML Sitemap, Schema.org Metatag — provide enterprise-grade SEO infrastructure. Drupal 11.4 even added default robots.txt rules that block crawlable search-parameter URLs. The platform isn’t the limitation. Configuration, content architecture, and deployment discipline decide whether a Drupal site ranks or slowly loses ground.
This is what we call GEO — Generative Engine Optimization — and Drupal is well-positioned for it. AI engines read the raw HTML your server returns, not JavaScript-rendered content, and Drupal renders server-side by default. We build on that with valid JSON-LD structured data, extractable content structure, entity consistency, and Drupal’s LLM-optimized content tooling where it fits. AI engines cite only a handful of sources per answer — the work is making your content the one they can parse and trust.
Both, depending on your team. If you have Drupal developers, we deliver implementation-ready tickets — severity, affected URLs, evidence, the fix, acceptance criteria — so your devs execute without ambiguity. If you need us to implement, we configure Metatag, Pathauto, Redirect, Simple XML Sitemap, Schema.org Metatag, Config Split, and other SEO-adjacent modules directly. Custom module development and deep Twig template work is scoped separately and coordinated with your dev team.
For an audit: a read-only crawl of the live site plus, ideally, admin or appropriate access to review configuration, and access to Google Search Console and Analytics. For implementation: a role-appropriate Drupal account (we work within your permissions, not shared logins), plus Search Console and Analytics. For headless projects, access to the front-end repository or a staging environment. We work through your access system and never need shared credentials.
No. The Standard plan is month-to-month with no cancellation fee. The free audit has no commitment attached. Longer terms only apply where you want them — enterprise, migration, or white-label engagements where a defined term helps both sides plan.
The standard stack on almost every project: Metatag (metadata with token defaults), Pathauto (clean URL aliases), Redirect (301 management), Simple XML Sitemap (entity- and Views-aware sitemaps), Schema.org Metatag (JSON-LD structured data), and Config Split (environment-specific configuration isolation). For content-model-first structured data, Schema.org Blueprints. For AI search, the Markdownify module and AI LLM Optimized Content recipe where they fit. Modules provide controls — strategy, configuration, and QA decide whether they produce good SEO.
That’s exactly what migration SEO is for. A D7→D11 move is a full migration — content model mapping, module replacement, theme rebuild, URL preservation. Every indexable URL is inventoried before we start. Every redirect mapped one-to-one — never bulk-redirected to the homepage. Every canonical, heading, schema output, and Metatag token validated against a pre-migration baseline. Search Console, server logs, rankings, and traffic monitored for 90 days post-launch, with a documented recovery protocol. Anyone who guarantees zero ranking loss on a D7 migration is either inexperienced or overpromising — but the methodology gives you the best possible chance.
Yes. Headless Drupal creates specific challenges: metadata must be generated by the front-end framework from Drupal’s API, canonicals must point to the front-end domain, sitemaps must reflect rendered URLs, internal links must be crawlable without JavaScript, and structured data must render server-side. This last point matters doubly for AI search — AI crawlers don’t execute JavaScript, so client-side-only content is invisible to them. We define ownership boundaries between Drupal and the front end and enforce parity between what Drupal stores and what Google and AI engines receive.
It depends on your starting point. On a site with existing rankings but technical problems — Views crawl waste, misconfigured Metatag, taxonomy cannibalization — cleanup often produces measurable improvement within four to eight weeks as Google recrawls the consolidated URL surface. On a new or thin site needing content and authority, meaningful movement typically takes four to six months and compounds beyond that. On a migration, the immediate goal is preserving rankings at launch. We report on leading indicators — crawl behaviour, indexed-URL trends, keyword coverage — monthly, so you see progress before final rankings catch up.
No — and any Drupal SEO agency that does should be a red flag. Google’s own quality-rater guidelines flag ranking guarantees as a low-trust signal. Search results depend on your market, competition, starting authority, and Google’s ongoing changes. What we guarantee is the methodology: every service on this page delivered the same disciplined way every time. We’d rather earn your continued business with real results than lock you into a promise we can’t control.
Send us your Drupal site and we’ll show you the Views crawl traps eating your crawl budget, the taxonomy pages cannibalizing your real landing pages, the Metatag tokens rendering blank descriptions, the config deployment risks that quietly reset your SEO, and the gaps keeping you out of AI Overviews. You get a prioritized findings roadmap with developer-ready tickets — yours to act on with or without us.
