Ecommerce Digital Marketing

Your catalog is your content.
Most of it was never written.

A store with four thousand products has four thousand pages that were generated rather than authored — supplier copy, duplicated variants, a feed that disagrees with the page it came from. Google publishes a dedicated specification for ecommerce, and most catalogs do not meet it. Fix the product record and the page, the feed, the ad and the AI answer all improve at once.

We work with pure-play ecommerce operators, manufacturers selling parts catalogs, franchise systems with retail alongside service, medical and aesthetics practices with product lines, and mid-market and private equity portfolio companies with a commerce arm — a hundred SKUs or a hundred thousand.

One record
Page, feed and structured markup made to agree, then kept that way
AI-first
Product data built for the systems that summarize options before a shopper reaches you
Revenue
Reported against orders and margin, not sessions and last-click ROAS
Where Ecommerce Programs Leak Found in most catalogs
1
Supplier copy on every page The same words your competitors use
2
Feed and page disagree Two answers about one product
3
Variants competing with each other Six URLs for one product
4
ROAS optimized, margin ignored Growing the least profitable lines
Three Systems, One Product

The page says one thing. The feed says another.

Every product you sell exists in at least three places — the page a shopper reads, the feed that carries it into shopping surfaces, and the structured markup that machines read. When those three disagree, you have given three answers to the same question, and the systems deciding whether to show your product notice.

Three translucent product-record layers stacked in depth — the page, the feed and the structured markup — aligned for most items and visibly offset where they disagree
Documented
Google publishes a dedicated ecommerce section of its search documentation
Google Search Central — ecommerce
Specified
Product data requirements are published in full, attribute by attribute
Merchant Center product data specification
Must match
Structured product data must reflect what is actually on the page
Google — product structured data
Observed
Most catalogs we inherit have never had the three compared against each other
Allegiant observation, stated as such

This is unusually well documented, which makes it unusually fixable. Google maintains an entire ecommerce section in its search documentation, publishes the product data specification attribute by attribute, and states in its product structured data guidance that markup must reflect what is genuinely on the page. Almost none of this is ambiguous. What makes it hard is that nobody owns the product record.

Because ownership is split, the three copies drift apart quietly. Merchandising updates the page. An integration syncs the feed on its own schedule from a different source. The markup was generated by a theme two years ago and has never been touched. Each team is doing their job correctly and the result is a catalog that contradicts itself at scale — which is exactly the condition that makes a product hard to verify and easy to skip.

The compounding is the reason this is worth doing properly. One product record feeds the page, the shopping surfaces, the marketplace listings, the ads and increasingly the AI answers. Fix it at the source and every one of those improves simultaneously. Fix it in one destination and the next sync overwrites your work, which is why so many teams conclude that feeds are unreliable when the real problem is that no record was ever authoritative.

The AI shift raises the stakes rather than changing the work. Assistants increasingly summarize product options before a shopper reaches any store, and those summaries are assembled from structured product data — the same attributes that keep you eligible in shopping surfaces. Clean product data now pays twice: once in the auction, and once in whether an assistant names your product at all. Most ecommerce agencies are still optimizing for the click. Our method is on the AI SEO agency page, with the model layer under LLM optimization.

None of that helps if the economics underneath are wrong, which is the other half of this practice. A catalog optimized toward return on ad spend will faithfully grow whichever lines convert most easily, and those are frequently the lines you earn least on. Revenue is not the same as margin, and an agency that never asks which is which is optimizing a number that flatters both of us.

Product Content

Supplier copy is not content. It is your competitors' content too.

If your product descriptions came from the manufacturer, every other retailer selling that item has the identical words. There is nothing in that page for a search engine to prefer, nothing for an AI system to quote you on, and nothing that helps a shopper choose you rather than the cheapest listing.

Two racks of product cards side by side, one where every card carries the same supplied description and one where each card carries detail written for that product
Inherited

The same words, everywhere it is sold

  • Manufacturer copy pasted verbatim, identical across every retailer carrying the product.
  • Specifications only — dimensions and materials, with nothing about who it suits or why.
  • No comparison, so a shopper deciding between two of your own products gets no help.
  • Nothing quotable, which matters now that assistants answer by drawing on sources they can cite.
  • Competition on price alone, because price is the only variable left.
Written

Reasons to choose this one

  • Written for the product — what it is for, who it suits, where it falls short.
  • Real specifications kept, structured so machines can read them and shoppers can scan them.
  • Comparison built in, including honest guidance toward a different item when that is the right answer.
  • Questions answered on the page, which is what reduces returns as much as it increases orders.
  • Something to be cited for, in search results and in AI answers alike.
§
Nobody chose supplier copy cynically — it is what you get when a catalog needs four thousand descriptions and there is no process for producing them. That is why we start with the products that carry the revenue rather than attempting the whole catalog. A hundred well-written pages covering most of your sales is worth more than four thousand thin ones, and it is achievable this quarter. Our content practice handles the writing; the prioritization is a margin question we work out with you first.
Why Our Version Beats The Alternative

Four things we do that most ecommerce agencies will not.

Each of these is slower to start, harder to sell, and the reason a catalog actually earns. We will put all four in writing before an agreement is signed.

1
We reconcile page, feed and markup
Item by item, not sampled
ComparedAll three sources
ReportedEvery disagreement

Most audits check the feed against Merchant Center requirements and stop. We compare the feed against the live page and the structured markup against both, because a product that passes validation while contradicting its own page is still giving conflicting answers.

This is where the fastest wins usually sit — items disapproved or quietly suppressed for reasons nobody has looked at since the integration was built.

What this looks like in practice
  • Every item checked across all three sources, with disagreements listed rather than summarized.
  • The source of truth established so corrections stop being overwritten on the next sync.
2
Margin before ROAS
The number that pays you
We ask forMargin by line
Then optimizeToward profit

Return on ad spend treats every dollar of revenue as equal. Your accountant does not. A campaign optimized on ROAS will faithfully grow whichever products convert most readily, and in most catalogs those are not the products you earn most on.

We ask for margin by product line before building anything, and where a partner cannot supply it we say plainly that we are optimizing a proxy until they can.

What this looks like in practice
  • Campaign structure and bidding shaped by contribution rather than revenue alone.
  • Products that lose money at scale identified and named, even when they look successful.
3
Product pages built for two readers
The shopper and the machine
Reads wellFor a person
Parses cleanlyFor a system

The same page has to convince somebody choosing between three options and be machine-readable enough for a shopping surface or an assistant to represent accurately. Those are not competing goals — clear structure and honest specifics serve both.

Where they conflict, the shopper wins, because a page optimized for machines that nobody buys from has solved the wrong problem.

What this looks like in practice
  • Structured data that reflects the visible page rather than a parallel dataset.
  • Content prioritized by revenue so effort lands where it pays, via ecommerce SEO.
4
We report against orders
Not sessions, not last click
CheckedAgainst your platform
IncludingThe gap

Ad platforms report conversions they believe they caused. Your commerce platform records orders that actually happened. Those numbers rarely match, and the difference is not a rounding error — it is the space where budget decisions go wrong.

We reconcile monthly and report the gap, including in months where it makes our work look less impressive than the dashboard would.

What this looks like in practice
  • Platform-reported conversions traced to orders in your own system.
  • Returns and cancellations accounted for, because revenue that came back is not revenue.
Where The Record Breaks

One product record. Five places it has to be right.

The economics of catalog work are entirely determined by this diagram. A correction made at the source improves five surfaces; a correction made at a destination survives until the next sync.

Why the source of truth decides everything

A product's title, description, price, availability, identifiers and images appear on the product page, in the shopping feed, on any marketplace you sell through, inside your ads, and in whatever an AI system has absorbed about it. Nearly all of those are populated from somewhere upstream. Which means the useful question is never "is this listing correct" but "which system is the correct one, and does everything else read from it".

Marketplaces are where this most often breaks, because they are frequently fed by a different integration than the one serving your own site. A price change or a discontinued variant propagates to your store immediately and to the marketplace on a schedule nobody remembers configuring. The result is a shopper finding two different prices for the same item under your own brand.

Variants deserve specific attention because they multiply silently. A product in six sizes and four colours can generate two dozen URLs, most carrying near-identical content. Google's guidance on consolidating duplicate URLs exists precisely for this, and getting it wrong means your own variants compete with each other for the same queries while diluting whatever authority the product had.

The fix is unglamorous and it is the highest-leverage work in the account. One authoritative record per product, everything downstream reading from it, change control so a price update reaches every surface, and a reconciliation step that compares the destinations against the source on a schedule rather than when somebody notices. Once that exists, every other improvement compounds instead of eroding.

  • The product record — one per item, owned by somebody named
  • The product page — rendered from it, not maintained separately
  • The shopping feed — matching the page, attribute by attribute
  • Marketplace listings — usually a different integration, usually stale
  • The ads — drawing on the feed, inheriting whatever is wrong with it
  • The AI answer — assembled from all of the above, and unforgiving of contradiction
An engineering-style elevation tracing a single product record out to the store page, the shopping feed, the marketplace and the AI answer, with the disagreement point marked
How An Engagement Runs

Fix the data, prioritize by margin, then scale what actually earns.

Most ecommerce engagements start by launching campaigns against whatever the catalog currently says. We start by finding out what it says, because media spent against bad product data buys the wrong things efficiently.

1

Catalog and measurement

Days 1–30
  • Page, feed and structured markup compared item by item
  • Disapproved and suppressed items identified with their actual causes
  • Variant and duplicate handling audited across the catalog
  • Platform-reported conversions reconciled against orders in your system
You learn how much of your catalog is genuinely sellable today.
2

Priorities and content

Days 31–60
  • Products ranked by contribution rather than by revenue or volume
  • Source of truth established with change control that holds
  • Product content written for the items carrying the margin
  • Category and navigation structure corrected where it fragments authority
Effort lands on the products that actually pay for it.
3

Scale and reconcile

Days 61–90
  • Paid media scaled against verified margin signals rather than raw ROAS
  • Organic and AI visibility built on the corrected product data
  • Returns and cancellations folded into reporting
  • Monthly reconciliation against your commerce platform, gap included
Growth you can see in the bank rather than in a dashboard. Same standard as paid search.
Everything Included

What an ecommerce program covers

Product data underneath, channels on top. These are the pieces, and each is a practice you can read about and hold us to.

Catalog and feed management

Product data reconciled across page, feed and markup, with the source of truth established and change control that survives the next integration sync.

Runs with: Google Shopping

Ecommerce SEO

Category architecture, variant consolidation, faceted navigation and product content — the organic half, where a corrected catalog pays for years rather than for a flight.

Runs with: ecommerce SEO

Paid media across shopping surfaces

Shopping, search and automated campaign types managed against margin rather than raw return, with feed quality treated as the primary lever it actually is.

Runs with: ecommerce PPC and paid search

Store design and checkout

Product page structure, navigation at catalog scale, and the checkout friction that quietly costs more than any campaign will ever recover.

Runs with: ecommerce web design

Retention and lifecycle

Email and messaging driven by purchase history rather than a send calendar — the cheapest revenue in ecommerce and the most consistently under-run.

Runs with: email marketing and SMS

AI visibility for the catalog

The structured product data that keeps you eligible in shopping surfaces is the same data assistants read when they summarize options before a shopper reaches you.

Runs with: AI SEO and answer engine optimization

Who We Work With

A hundred SKUs or a hundred thousand, the discipline is the same.

Ecommerce is a capability several kinds of business need rather than a separate species of company. We run it for pure-play stores and for operators who sell products alongside everything else they do.

Pure-Play Ecommerce
Stores where the catalog is the business — deep product ranges, thin margins on some lines, and every decision downstream of product data quality.
Runs with: ecommerce PPC
Parts and equipment catalogs where specification accuracy is the whole purchase decision and a wrong attribute is a returned order.
Runs with: technical SEO
Product sales alongside service delivery, where the catalog is shared across units but fulfillment and availability are local.
Commerce assets held in a fund, where catalog health and margin visibility are diligence questions before they are marketing ones.
Runs with: market research
Practices selling product lines alongside treatment, where claims need care and the catalog supports the service rather than replacing it.
Runs with: reputation work
Established businesses adding a commerce arm, where the catalog has to work without a dedicated ecommerce team behind it.
Why Operators Choose Allegiant

We ask for your margins before we ask for your budget.

Return on ad spend is the standard ecommerce metric and it treats every dollar of revenue as identical. Your accountant does not. Before we structure anything we ask which product lines actually earn, and where a partner cannot tell us, we say plainly that we are optimizing a proxy until they can. That conversation is uncomfortable in week one and it is the reason our ecommerce partners stay past year three.

We built Allegiant as an AI-first agency rather than a traditional shop that added AI to a service list. In a catalog that difference is concrete: the structured product data that keeps items eligible in shopping surfaces is the same data assistants read when they summarize options before a shopper reaches your store. Treating product data as a technical chore rather than as the visibility strategy is the most common mistake in the category, and it gets more expensive every quarter.

Ecommerce runs alongside SEO, paid social, remarketing and the full digital program. See the work in our case studies.

25
Years buying and building media for operators
US & CA
Partners served across both countries
Credentials
Google Partner
Verified
Semrush Certified Agency
Verified
Certified CallRail Agency
Verified
Inc. Power Partner
2024 and 2025
50PROS Top 10 Global
Awarded
BBB A+ Accredited
Accredited
Listed Versus Selling

The catalog you own and the catalog that earns.

Every row narrows, and each narrowing has a different cause and a different fix. Knowing which step your catalog loses products at tells you where the next hour belongs far better than any traffic report.

A physical tally board with racked counters showing products listed, eligible, visible and actually selling, with the final row far shorter than the first
The count What most reports show Allegiant What we check
Products in the catalog The headline number The starting point, never the achievement
With complete data Assumed Checked against the published specification, attribute by attribute
Eligible to show Reported as a feed status Traced to causes, including items suppressed rather than disapproved
Actually seen by shoppers Aggregated into impressions Reported per product, so dead inventory is visible
Producing revenue A single revenue figure Broken out by line, net of returns and cancellations
Producing margin Not reported The only row that answers whether the program worked

The last row is the one your accountant already knows and your marketing report usually does not. If your agency has never asked for margin by product line, they are optimizing a number that can rise while the business gets worse.

What We Decline To Sell

Four ecommerce line items you can stop paying for.

Each is common, each looks like progress, and each can rise while the business gets worse. We would rather lose the line item than defend it.

ROAS reported as the outcome. It treats a dollar of revenue on your worst-margin product as identical to a dollar on your best. A campaign can improve its return on ad spend every month while shifting your sales mix toward the products you earn least on, and the report will look excellent throughout.

Bulk-generated product descriptions. Four thousand thin pages produced automatically give a search engine no reason to prefer any of them and give a shopper nothing to decide on. A hundred well-written pages covering most of your revenue is worth more and is achievable this quarter.

Feed management sold as a subscription with no source of truth. Correcting the same attributes every month is not maintenance, it is a symptom. If no system is authoritative, the errors return on the next sync and the recurring fee is a subscription to the problem.

Traffic growth reported without returns. Revenue that came back is not revenue. Any ecommerce report that never mentions returns or cancellations is describing gross orders, which is the number furthest from what you actually banked.

The pattern beneath all four: in a catalog, the easiest number to grow is rarely the number that pays you.

Evidence note. Platform requirements described on this page are drawn from Google's own published documentation, linked at the point of use and read live on the review date in the byline. Google's documentation is vendor documentation — authoritative for how its own systems behave and not independent research. Product data requirements, eligibility rules and shopping surface behavior change without notice; confirm current requirements in your own Merchant Center account rather than relying on this page. Statements about what we observe in inherited catalogs are Allegiant observations and are labeled as such in the text. Where we describe how AI systems use product data, that is our working view based on published platform guidance rather than documented mechanics — the platforms do not publish their selection logic. No conversion-rate, return-on-ad-spend, traffic, revenue, margin or cost figures appear anywhere on this page, and no pricing is quoted, because those vary by category, catalog and season and date immediately. Advertising claims, pricing representations and the use of customer reviews carry their own federal obligations; nothing here is legal advice and your counsel is the right reader for your position.
Questions Operators Ask

Ecommerce digital marketing, answered

Straight answers, including the ones that cost us work.

Platform requirements change without notice. Confirm anything platform-specific in your own account before acting on it.
Where should an ecommerce program start?+

With the product data, every time. Google maintains a dedicated ecommerce documentation section and publishes its product requirements in full, so most of what determines whether your items can be shown is knowable rather than mysterious. Media spent against a broken catalog buys the wrong things efficiently. We audit the data first and tell you how much of your catalog is genuinely sellable before we recommend spending anything — the same sequencing our ecommerce SEO practice follows.

Why do our products keep getting disapproved?+

Usually a mismatch between the feed and the page, or a missing required attribute. The product data specification lists exactly what is required for each category, and the shopping ads policies govern what may be advertised. What most teams miss is that items can be quietly suppressed rather than formally disapproved, which produces no alert at all. That is why we compare the feed against the live page rather than only against validation — the approach on our Shopping page.

Should we rewrite every product description?+

No, and attempting it is how catalog content projects die. Start with the products carrying your revenue and margin, which in most catalogs is a small fraction of the items. Supplier copy is identical across every retailer selling that product, so there is nothing for a search engine to prefer or an assistant to cite you on — but that only matters where the product can actually earn. Google's guidance on helpful, people-first content applies as much to a product page as an article. Our content team handles the writing.

How should product variants be handled?+

Deliberately, because they multiply silently. A product in six sizes and four colours can generate two dozen near-identical URLs that compete with each other and dilute whatever authority the product had. Google's guidance on consolidating duplicate URLs covers the mechanics, and the right answer depends on whether shoppers genuinely search for the variant or only for the product. Getting it wrong is one of the most common and most expensive catalog defects. Detail on ecommerce SEO.

Why do you ask for margin data before building campaigns?+

Because return on ad spend treats every dollar of revenue as equal and your accountant does not. A campaign optimized on ROAS grows whichever products convert most readily, which in most catalogs are not the ones you earn most on — so the metric improves while the sales mix gets worse. Where a partner cannot supply margin we say plainly that we are optimizing a proxy until they can, rather than pretending the proxy is the goal. The full approach is on our ecommerce PPC page, and the reconciliation runs through your systems, against the campaign types documented in Merchant Center's product category guidance.

How is AI changing ecommerce marketing?+

Assistants increasingly summarize product options before a shopper reaches any store, and those summaries are assembled from structured product data — the same attributes that keep you eligible in shopping surfaces. So clean product data now pays twice, once in the auction and once in whether an assistant names your product. The work has not changed; the cost of skipping it has. We do not claim to control what any assistant says, because nobody does — the honest position is on our GEO page, and Google's product markup guidance is the foundation.

Our ad platform and our store report different numbers. Which is right?+

Your store, for the purpose of deciding anything. Ad platforms report conversions they believe they caused, using their own attribution windows and models; your commerce platform records orders that actually happened. The gap is normal and it is not a rounding error. What matters is that somebody reconciles them monthly and reports the difference rather than quoting whichever number flatters the work. We also net out returns, because revenue that came back is not revenue — the same standard applied across every paid engagement and grounded in measurable page experience on the store side.

We sell on marketplaces as well. Does that complicate things?+

It is usually where the record breaks first, because marketplaces are typically fed by a different integration than your own site. A price change or a discontinued variant reaches your store immediately and the marketplace on a schedule nobody remembers setting, so a shopper finds two different prices under your own brand. The answer is one authoritative product record with everything downstream reading from it, plus a reconciliation step on a schedule rather than when somebody notices. Google's shopping policies treat accuracy as a requirement, not a preference. Keeping the destinations in step is part of our record distribution discipline.

Do customer reviews on product pages carry any legal risk?+

They carry obligations worth knowing about. The FTC's rule at 16 C.F.R. Part 465 addresses consumer reviews and testimonials, and the endorsement guides cover incentivized and affiliated reviews in detail. Google's review snippet guidance governs how they may be marked up. In practice the rules reward what a good store does anyway — collect reviews honestly, disclose incentives, do not suppress unfavorable ones selectively. Nothing here is legal advice and your counsel governs your position. Our approach to review programs is on the reputation page.

How long before an ecommerce program shows results?+

Data corrections can move quickly, because an item that was ineligible becoming eligible is a step change rather than a climb. Content and organic authority take longer and vary by category and competition. Paid can move immediately and will simply spend faster on a broken catalog, which is why sequencing matters. We will not quote a single timeline for a whole catalog — a product with a missing attribute and a product in a saturated category are different problems on different clocks. The A.R.C. Report tells us which is which, and Google's own ecommerce guidance is candid about the same point.

We are not a pure ecommerce business. Does this still apply?+

Yes, and it is a large part of who we do this for. Manufacturers with parts catalogs, franchise systems selling product alongside service, practices with retail lines and mid-market operators adding a commerce arm all face the same product data problem without a dedicated ecommerce team behind it. The catalog discipline is identical; what changes is that the store supports the business rather than being the business, which usually simplifies the margin question considerably. The same feed requirements apply whether the catalog is your whole business or part of it. Related: manufacturing and franchise systems.

What makes Allegiant different from the ecommerce agency we use now?+

Three things you can verify. We reconcile page, feed and markup item by item rather than checking the feed alone. We ask for margin by product line before structuring anything and tell you when we are optimizing a proxy instead. And we reconcile platform-reported conversions against orders in your own system monthly, net of returns, including when the gap is unflattering. We are also built as an AI-first agency rather than a traditional shop with AI added on. Start with the A.R.C. Report, or read the FTC's advertising guidance against whatever your current agency claims.

Find out how much of your catalog can actually be sold.

The A.R.C. Report covers your whole marketing position. For an ecommerce operation we compare your product page, feed and structured markup item by item, identify what is disapproved or quietly suppressed, and check whether reported conversions match orders in your own system. Findings are yours whether or not we work together.

What the review covers on an ecommerce operation
  • Product page, feed and structured markup compared item by item
  • Disapproved and quietly suppressed items identified with causes
  • Variant and duplicate handling audited across the catalog
  • Category and navigation structure checked for fragmented authority
  • Platform-reported conversions reconciled against orders in your system
  • A straight answer on which product lines are not worth advertising

Explore the wider program: ecommerce SEO, ecommerce PPC, ecommerce web design, all services and the A.R.C. Report.

Request an A.R.C. Report

Tell us your platform and roughly how many products you carry, and we will show you what the catalog looks like today.

No cost, no commitment. We will follow up by email or phone to walk you through the findings.