Technical SEO Remediation
Canonical strategy for /products/ versus /collections/products/, robots.txt.liquid rules, parameter handling, pagination, sitemap hygiene and crawl-budget recovery.
Ranking for the part number, the cross-reference and the spec query — the searches that end in a purchase order.
Delivered remotely for brands across Pittsburgh and Pennsylvania.
The most valuable search term for a lot of Pittsburgh businesses gets fewer than twenty searches a month and converts at a rate a consumer brand would not believe. It is a part number, a cross-reference to a discontinued item, or a specification string typed by someone with a machine down. Multiply that by several thousand and you have an organic channel that quietly feeds the sales desk. Most local catalogues have those pages and have never optimised a single one of them.
The competition is not other Pittsburgh companies. It is the marketplaces: the national MRO distributors, Amazon Business, and the aggregator sites that scraped your catalogue years ago and now outrank you for your own part numbers. Beating them does not require more content. It requires the things they cannot do — genuine cross-reference and compatibility data, real stock and lead-time signals, application guidance written by someone who has actually specified the product, and a collection architecture built around how an engineer narrows a choice rather than around your internal product hierarchy.
Then there is the platform tax. Shopify serves products at two URLs by default, faceted navigation on a large technical catalogue can generate an enormous number of crawlable parameter combinations, and collection pages ship with no copy and no internal linking. On a forty-product store none of that matters much. On twelve thousand SKUs it decides how much of your catalogue Google ever sees. We fix the crawl foundation before writing a word of content.
Two things make Pittsburgh SEO distinct. First, the collection map has to be built on specifications rather than categories. Buyers here narrow by material, size, pressure rating, thread type, temperature range, certification or equipment compatibility, so those need to be indexable landing pages with copy and internal links, not just filter states hidden behind parameters. Getting that right converts a filter system into hundreds of pages that each match a real query. Second, technical buyers were early adopters of asking an assistant before a search engine — 'what replaces this discontinued part', 'what fits this machine' — and answer engines will cite whoever publishes clean, extractable, entity-correct data. That is generative engine optimisation, and for a specification catalogue it overlaps almost perfectly with the schema and structured data work you should be doing anyway. The consumer side of the city is different again: a Strip District food importer or a Lawrenceville brand needs genuine local and category rankings, and there we do use the neighbourhood and the city, because people search that way for food, gifts and merchandise and never search that way for valves.
The same standard of work we run for every client — applied to a Pittsburgh brand’s realities.
Full service detailCanonical strategy for /products/ versus /collections/products/, robots.txt.liquid rules, parameter handling, pagination, sitemap hygiene and crawl-budget recovery.
A collection map built from real search demand, including sub-collections for attributes buyers search on: size, material, use case, price band, occasion.
Titles, descriptions, image alts, Product and Offer schema with live price and availability, plus review markup that stays valid as inventory changes.
Buying guides, comparisons and category explainers targeting mid-funnel demand, each linked into the collections they support. No filler blogging.
Entity and schema work, clean extractable answers, llms.txt and citation-worthy content so ChatGPT, Perplexity and AI Overviews reference your store.
Targeted outreach for editorial links to collection and guide pages from publications your buyers actually read. No directories, no link farms.
We do not work off a rate card. Every Pittsburgh engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.
Get this scopedA full crawl plus log-file analysis to find what Googlebot actually sees and where crawl budget is being spent. Findings ranked by revenue impact.
Keyword research mapped to your catalogue and margin, not to search volume alone. High-volume terms you cannot profitably serve get cut.
Technical remediation ships first. There is no point building content on a site that wastes half its crawl budget on filter URLs.
Collection landing pages and commercial content shipped on a fixed monthly cadence, each with internal links planned before it goes live.
Monthly reporting on non-branded organic revenue, index coverage and AI citations. Branded queries are excluded from every growth number we show you.
Anonymised under NDA. Figures pulled from the client’s own analytics.
8-figure DTC brand, ~140 SKUs, US + CA · Shopify Plus (migrated from Magento 2)
Magento 2 cost $9k a month in hosting, extensions and emergency dev before a single feature shipped. Mobile LCP sat at 5.4 seconds and mobile converted at less than half the desktop rate across 68% of sessions. The named constraint: 11,412 indexed URLs and a top-3 organic position on their hero category, so a migration that lost rankings would cost more than the platform ever saved.
~$7M/yr, 480 SKUs, US + EU via Shopify Markets · Shopify Plus (Shopify Markets, 3 regions)
Paid social carried 81% of revenue and CAC had climbed 44% in eighteen months. Organic sat at 2,100 sessions a month against category competitors doing ten times that, and the EU storefront duplicated the US catalogue with no hreflang at all. The named constraint: three national retailers own the head terms with link profiles this brand could not match in a year, so the plan had to win on query depth instead of authority.
“Honestly I signed for the SEO and the AI-search piece was a footnote in the proposal I skimmed. Then in March our product pages started getting quoted in ChatGPT answers for insulated growler queries, and that traffic showed up in GA4 with real purchase intent attached to it. Organic revenue is up 58% year over year and roughly a fifth of that comes from surfaces that didn't exist when we signed the contract. I still don't fully understand it. I've stopped questioning it.”
Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.
Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.