
A South African outdoor gear retailer refreshes its Shopify theme. The old template had a dedicated H1 field; the new one bakes the headline into a hero image. Within a week, product pages that ranked for “waterproof hiking boots Cape Town” lose their primary heading. No copy changed - the keywords physically moved. That is the core truth of keyword placement in web design: placement is governed by template fields and front-end modules, not by copywriters. This playbook shows how to make templates carry the right keyword slots so every new page inherits good placement by default.
Why Keyword Placement Is a Template Decision, Not a Copywriting Decision
Google’s SEO Starter Guide is explicit: there is no keyword-density magic. What matters is that the page clearly describes its topic, uses descriptive headings, and has unique, helpful titles. Those are structural fields your CMS exposes. If the template lacks an H1 field, the copywriter cannot place a keyword there. If the product template auto-generates the title as “Product Name - Store Name”, there is no room for a category modifier. The design team owns the slots; marketing fills them. Until that division is explicit, placement drifts with every redesign.
The Placement Map: Where Each Keyword Element Lives in a Modern CMS
Think of a page as a set of containers, each holding one placement opportunity. The table maps typical Shopify or WooCommerce fields to the on-page element they control and what the template must expose. Use it as a design specification.
| CMS Field (Shopify / WooCommerce) | On-page element | What the template must expose |
|---|---|---|
| Product title / Post title | H1 & title element (default) | Editable H1 field separate from product name; optional custom title field |
| Description / Body copy | Paragraphs, H2/H3 via rich-text editor | Allow H2-H4 in rich-text; lock heading order where needed |
| URL handle / slug | URL slug | Short, descriptive slug field editable at creation |
| SEO title / Meta description | Title element & meta description | Dedicated fields; fallback to product name is not enough |
| Image alt text | Alt attribute | Per-image alt field, not a bulk uploader default |
Tip: Treat the placement map as a design deliverable. If a field is missing, the template is not ready for content - regardless of how it looks in Figma.
One Primary Intent Per Page - Mapping Keyword Clusters to Template Types
Keywords are entities belonging to an intent cluster, not strings to sprinkle. Each template type should carry exactly one primary cluster. Mixing product and category intent on one template creates cannibalisation no copy editing can fix.
Category, Product, Blog and Landing Templates Each Carry Different Keyword Jobs
Internal Anchor Text: The Placement Decision Your Navigation Module Makes For You
Google’s link best practices recommend descriptive anchor text that tells users and search engines what the linked page is about. In a template-driven build, that decision is baked into the navigation module. A “Related products” module emitting “View product” gives Google nothing; one emitting the product name gives context. Designers should specify the anchor text source field for each module - product name, category name, or a custom SEO label. At Prebo Digital, our web design engagements treat this as a template-level requirement, not a post-launch tidy-up.
Which Module Emits Descriptive Links - Nav, Breadcrumbs, Related Content or In-Body
Breadcrumbs usually produce clean, hierarchical anchor text (e.g. “Outdoor > Footwear > Hiking Boots”). Related-content modules are the weakest - they default to generic phrases. Map each module to a field: nav items use menu labels, breadcrumbs use category names, related products use product titles, and in-body links use the editor’s custom anchor text. This prevents the silent leak where half a site’s internal links are non-descriptive.
Structured Data as Entity Placement: Product, Organization and BreadcrumbList
Structured data does not place a keyword in visible copy, but it clarifies the entity to search engines. For a South African store, Product schema with name, brand, and offers (in ZAR) reinforces what the page sells. Organization schema on the homepage and BreadcrumbList on inner pages make the hierarchy machine-readable. These are template-level outputs requiring the design team to expose fields and development to render JSON-LD consistently. Without that, rich results eligibility is left to chance.
The Placement Audit: A Repeatable Template Review Before You Ship
Before switching on a new template, run a field-by-field audit. This is the checklist we use for Shopify and WooCommerce stores.
| Checkpoint | Shopify field | WooCommerce field |
|---|---|---|
| Editable H1 separate from product name | theme setting or metafield | custom field |
| Unique SEO title per page | SEO title field | SEO plugin title field |
| Editable meta description | meta description field | SEO plugin meta description |
| Image alt text field | alt text on each image | attachment alt |
| Descriptive anchor text source | product title or custom label | category name or custom |
What to Check Field-by-Field in Shopify and WooCommerce
For Shopify, confirm the product template exposes the SEO title field and that the H1 is not hardcoded as the product title (some themes do this). For WooCommerce, check that the SEO plugin’s fields are not hidden on the category taxonomy screen - a common oversight. Verify image alt fields are not overwritten by the filename on upload. Small checks prevent large placement regressions.
Sources
- Google Search Central - SEO Starter Guide
- Google Search Central - Influencing title links in Google Search
- Google Search Central - Meta tags and attributes that Google supports
- Google Search Central - Image SEO best practices
- Google Search Central - Link best practices for Google
- W3C WAI - Page Structure Tutorial: Headings




