SEO for product teams: the ten things that actually move the needle.

Most SEO content is written by content marketers for content marketers. It focuses on keyword research, editorial calendars, and link-building outreach. That advice isn't wrong, but it's incomplete — and for product teams building web applications, it misses the levers that have the biggest impact. The things that actually move ranking for product pages are almost entirely technical: performance, structure, and architecture.

This post covers the ten things we've seen move the needle on every product we've shipped. Not theory — these are the changes that correlated with ranking improvements across twenty-plus client sites over the last two years. Some are obvious. Some are surprisingly underused. All of them compound.

§ 01The gap between SEO advice and SEO practice

If you search "how to improve SEO" right now, the first page of results will tell you to write better content, build backlinks, and use keywords in your headings. That advice works for blogs. It does not work for a SaaS product page, a Shopify storefront, or a web application with dynamic routes.

Product pages have different problems. Their content is often thin because it's generated from a database. Their URLs are often ugly because they're generated from an ORM. Their performance is often poor because they're rendered client-side with a JavaScript bundle that takes 2.5 seconds to hydrate. These are engineering problems, not editorial ones, and they require engineering solutions.

Here are the ten, in order of impact.

§ 02Core Web Vitals — the only metrics that matter

1. Get LCP under 2.5 seconds on mobile. Largest Contentful Paint is the single most important performance metric for SEO. Google has been explicit about this since 2021, and the data backs it up. Every site we've moved from the 3-4 second range into the sub-2.5 range has seen measurable ranking improvement within 60 days. The fix is almost always the same: reduce the critical rendering path. Server-render the above-the-fold content. Lazy-load everything below it. Serve images in WebP or AVIF at the correct dimensions. Use a CDN with edge caching.

2. Eliminate CLS entirely. Cumulative Layout Shift below 0.1 is the threshold, but aim for zero. The most common causes on product sites are images without explicit dimensions, fonts that swap visibly, and dynamic content that pushes the page down after initial render. Set width and height on every image element. Use font-display: optional or preload your web fonts. Reserve space for any content that loads asynchronously.

3. Keep INP under 200ms. Interaction to Next Paint replaced FID in 2024 and it's a harder bar to clear. It measures the delay between a user interaction and the visual update. Heavy JavaScript frameworks with large hydration costs fail this metric routinely. The fix is usually to reduce the amount of JavaScript that runs on interaction — defer non-critical scripts, split your bundles, and avoid synchronous rendering on click handlers.

The fastest SEO win is almost always a performance win. Fix LCP and CLS before you touch a single word of copy.

§ 03Structured data and rich results

4. Add JSON-LD structured data to every page type. Product pages get Product schema. Articles get Article schema. FAQ sections get FAQPage schema. This isn't optional anymore — pages with structured data are significantly more likely to appear in rich results, and rich results get dramatically higher click-through rates. We've measured 30-60% CTR improvements on pages that went from plain blue links to rich snippets with ratings, prices, or FAQ dropdowns.

5. Use BreadcrumbList schema on every page. This is the single most underused piece of structured data. It costs five minutes to implement and it gives Google explicit information about your site hierarchy. It also generates breadcrumb trails in search results, which improve CTR and help users understand where they are in your site before they click.

§ 04Content architecture over content volume

6. Build topic clusters, not isolated pages. A single page targeting "project management software" will not rank. A cluster of twenty pages — a pillar page on project management, supporting pages on Gantt charts, task dependencies, resource allocation, team capacity planning — linked together with clear internal structure, will. Google's understanding of topical authority means that depth matters more than breadth. Write fewer pages, but make each one the best resource available on its specific topic.

7. Internal linking is your most powerful free tool. Every page on your site should link to at least three other pages on your site. The anchor text should be descriptive, not generic. "Learn more" tells Google nothing. "Our guide to task dependency mapping" tells Google exactly what the linked page is about. We audit internal links on every project and typically find 40-60% of pages with zero internal links pointing to them. Those pages are invisible to search engines.

8. URL structure should mirror your information architecture. /blog/seo-tips is fine. /blog/2026/03/14/seo-tips-for-product-teams-updated-guide-v2 is not. Keep URLs short, descriptive, and stable. Never put dates in URLs unless the content is genuinely time-bound. If you restructure your site, implement 301 redirects for every old URL. A single wave of unredirected URLs can cost months of accumulated ranking authority.

§ 05The technical audit checklist

9. Run a technical audit quarterly. Not a content audit — a technical one. Here's the checklist we use:

# Technical SEO quarterly audit
01. Crawl the site with Screaming Frog or Sitebulb
02. Check for 404s, redirect chains, soft 404s
03. Verify canonical tags on every page
04. Validate robots.txt and XML sitemaps
05. Check Core Web Vitals in CrUX (real user data)
06. Verify structured data with Rich Results Test
07. Audit internal links — find orphaned pages
08. Check mobile rendering (not just responsive layout)
09. Verify hreflang tags if multilingual
10. Review server response codes and TTFB by page type

This takes about four hours per quarter for a site with 500 pages. The ROI is enormous. We've found broken canonical tags that were de-indexing entire product categories, redirect loops that were eating crawl budget, and soft 404s that were diluting the authority of high-value pages. None of these are visible to users. All of them are visible to Google.

§ 06Engineering-grade SEO vs content farming

10. Stop publishing content for the sake of publishing. The era of "publish three blog posts a week and rank through volume" is over. Google's helpful content updates in 2023 and 2024 penalized exactly this pattern. What works now is fewer, better pages — each one technically sound, structurally clear, and genuinely useful to the person who lands on it.

Engineering-grade SEO means treating search optimization the same way you treat performance optimization: with data, with measurement, with iteration. You instrument your pages. You measure their Core Web Vitals in the field, not just in Lighthouse. You track ranking changes against technical changes and build a causal understanding of what moves your specific site.

Content farming is guessing. Engineering-grade SEO is measuring. The ten items above are the things we've measured that work. They're not glamorous. They don't require a content team of twenty. They require an engineer who understands HTML, performance, and how crawlers see the web. If you have one of those — and if you're reading this, you probably are one — the ranking improvements are already within reach.

Start with LCP. Everything else follows.

— End of essay. Need help with a technical SEO audit? Start a project →