8 parts · 1 checkpoint · 3 free / 5 member parts →
Series start
From content map to page template
The content map assigns page roles; the page template decides which structure can repeat and which facts must be confirmed page by page. Neither is permission to publish the template everywhere.
SEO Advanced 03
Template strategy is not about which layout looks nice. It defines what search, trust, and conversion jobs collections, products, articles, hubs, and policy pages each own.
The store sells dog raincoats, and one decision shows whether the team has thought about template responsibility: does the size table go in the template, in a section, or on each page? Waterproof, reflective and raincoat-plus-leash products share one PDP template, but chest and back-length ranges differ, and the leash set also has to say what fits the coat and what fits the leash. The answer: the table goes in a section; the ranges go into per-page facts. The section guarantees every PDP carries the table; the ranges cannot be hard-coded in the template, because a hard-coded range shows the wrong sizes for one product family. The tempting mistake is putting everything in the template: it saves work, but the reflective cut runs a size narrower than the waterproof one, so the template immediately adds "sizing is off" to the return reasons.
A template decides what can repeat and what has to be written per page, and the matrix records page type, search task, required blocks, forbidden uses, structured data and the checker.
- Turn templates into reusable SEO assets instead of redesigning every page by feel.
- Reduce intent confusion between collections, product pages, and articles.
- Page template
A page template is the structural promise for a page type: information order, page blocks, links, structured data, and conversion entry. If misread Copying the visual style without the search task and evidence structure.
- Template responsibility
Template responsibility defines what this page type should solve, route, and not own. If misread Making product pages teach everything, articles handle transaction, and collections offer no decision criteria.
- Page block rules
Page block rules define when reusable FAQs, comparison tables, sizing charts, trust proof, recommendations, and related content should appear. If misread Putting the same page blocks everywhere, making pages bloated and unclear.
- Change check rule
A change check rule defines who can change templates, what must be checked, and what data to review after launch. If misread Ad hoc template edits break links, schema, headings, and conversion paths together.
Which columns the page template matrix needs
This matrix sits next to the template file: who owns it, how deep it reaches, what must be written per page, and what to check when it breaks. Every field must produce a next action.
Collections, product pages, articles and policy pages cannot carry the same responsibility. The matrix spells that out.
- Read
- Check whether it owns category choice and transaction entry.
- Do this
- Add decision criteria, filters, products, FAQs, and related content.
- Avoid
- Do not make it only a product list.
- Read
- Check specs, trust, shipping, returns, and usage boundaries.
- Do this
- Add proof, FAQs, sizing/specs, and related content entries.
- Avoid
- Do not force product pages to own broad comparison terms.
- Read
- Check whether it solves learning, comparison, or troubleshooting.
- Do this
- Give articles clear next-step links and commercial paths.
- Avoid
- Do not end with no path forward.
- Read
- Check promises, rules, contact paths, and support boundaries.
- Do this
- Connect policies to products, checkout, FAQs, and ad promises.
- Avoid
- Do not turn policy into an unreadable legal wall.
Pro · Parts 3-7 · 5 parts
Members: full exercises and records
This part includes
- Templates hold structure; facts stay per page
- Reuse passes the responsibility matrix
- Template changes need an owner and review
1 self-check question
Pro $20 / monthYearly $16 / month
Choose a plan, sign in with your email or Google account, and complete payment. You'll have instant access to all member benefits.
- Unlock every premium lesson
- Advanced tools and member resources
- Member-requested courses and ongoing updates
- Pro community and priority support
Checking your membership…
What's the difference between monthly and yearly?
Yearly plans save you 20% with annual payment. Monthly plans offer more flexibility for short-term needs.
FAQ
- How should collection pages, product pages, articles, and policy pages divide SEO jobs?
Start from the user task. Collection pages own comparison, filtering, and product entry. Product pages own facts for one SKU, including specs, price, availability, reviews, and buying risk. Articles own steps and explanation. Policy pages own return, damage, shipping, and exception rules. The page template responsibility matrix should record the primary search task, required page blocks, should-not-own intent, structured data boundary, and validation evidence.
- Which pages can use repeatable templates, and which need custom page copy?
Structure can repeat: filters, product grids, FAQ sections, breadcrumbs, spec tables, and structured-data reading. Judgment cannot be copy-pasted: who a collection fits, a product dimension or setup limit, an article failure case, or the trigger and exception rules on a policy page.
- Can Product structured data or Breadcrumb structured data fix the wrong page template?
No. Structured data describes visible content; it does not turn an article into a PDP or replace real navigation. When the template is wrong, fix page responsibility and visible content first, then use Product structured data, Breadcrumb structured data, FAQ, or Article markup only where it matches the page.
Continue reading
Connect template responsibility to the content map and technical governance
Page templates reuse structure, content maps assign each URL a page role, and technical governance continues with canonical, pagination, crawl, and indexing checks.
Return to the SEO Advanced Hub: SEO Advanced Hub