Why This Matters
The structure of a site determines how it ranks.
Getting it wrong before build means rebuilding later.
Most e-commerce site rebuilds carry the same structural mistakes from the old site into the new one. URLs that don't match buyer language. Categories that reflect internal logic instead of search demand. Pages missing where demand exists. This engagement prevents that.
The Risk Without IA
URL changes after launch cost rankings. Navigation changes after build cost development time. Category naming decisions made by feel rather than data leave search volume on the table from day one. Every structural mistake compounds over time.
The Timberfix-Specific Constraint
WooCommerce begins to degrade at 50 product variables. Timberfix products carry up to 175. Without deliberate architecture that accounts for this upfront, the new site inherits the same constraints as the current one, just on a newer theme.
This blueprint is a pre-build engagement. Every page, URL, navigation path, content requirement, and keyword is defined and validated before a line of code is written. The investment protects the build and the SEO value the new site is designed to generate.
What's Included
Six deliverables. One complete blueprint.
Every component is produced as part of a single, connected engagement, so URL structure informs navigation, keyword research validates both, and the description framework maps directly to the final page inventory.
00
Discovery, Kickoff & Catalogue Briefing
A structured working session with the Timberfix team to map product categories, understand range depth, and capture internal naming conventions before research begins. Everything else is built on what we learn here.
Foundation
01
Sitemap
A complete inventory of every page on the new site, categorised by page type, template, hierarchy, and crawl priority. The master reference for design and development.
Page Inventory
02
Navigation Architecture
Primary navigation hierarchy, mega menu structure, breadcrumb logic, mobile nav, and footer, all mapped to the final category taxonomy before design begins.
UX + SEO
03
URL Structure
Clean, keyword-informed URL patterns across every page type. Designed to scale as Timberfix's range grows.
Taxonomy
04
Product Description Framework
A matrix defining exactly which pages need short descriptions, long copy, or spec-only, with a template for each. Resolves the variable complexity problem at the content level.
Content Matrix
05
Keyword Research & Page Title Validation
Search demand mapped to every node in the sitemap. Category names, page titles, H1s, and URL slugs validated against real keyword data, so the site is built around how buyers actually search, not how Timberfix internally categorises products. Gap pages identified where demand exists but no page does.
SEO Foundation
00
Discovery, Kickoff & Catalogue Briefing
Foundation
What you receive
A structured working session that surfaces everything we need to know before research begins. The IA can be validated against keyword data, but product knowledge, internal naming conventions, and category logic live inside Timberfix. This session captures it.
What gets covered
- Product catalogue walkthrough: categories, subcategories, range depth, and edge cases
- Internal naming conventions vs. buyer-facing language and where they diverge
- Known gaps in the current site structure (categories missing, pages that shouldn't exist)
- ERP or stock system data access, including what's available and in what format
- Trade account requirements and how the portal fits the catalogue structure
- Agreed scope, milestones, and review cadence for the engagement
Why it comes first
Every deliverable that follows (sitemap, URLs, navigation, content framework, keyword research) is shaped by what we learn here. Starting research before this session risks building the wrong architecture around the wrong assumptions.
01
Sitemap
Page Inventory
What you receive
A complete, structured inventory of every page the new Timberfix site will contain — organised by type, template, and hierarchy. This becomes the master reference document for the entire project: design, development, and content are all scoped against it.
- Homepage, category landing pages (L1, L2, L3), and product detail pages
- Static pages: About, Contact, Trade Account, Store Locations
- Utility pages: Cart, Checkout, Account, Order Confirmation
- Content pages: Blog index, resource hub, product guides
- Template assignment per page type
- Crawl priority and depth for SEO
02
Navigation Architecture
UX + SEO
What you receive
Navigation is internal link architecture. Every item in the primary nav passes authority to its destination. Decisions made here (what top-level categories appear, in what order, how subcategories are grouped) directly determine which pages rank and how fast new products gain visibility.
- Primary nav: top-level category order and grouping logic
- Mega menu design: subcategory panels, featured product placement, quick-access links
- Breadcrumb structure across all category and product pages
- Mobile navigation hierarchy (built for users on-site and on-tool)
- Footer navigation: secondary categories, utility links, trade account
- Search bar prominence and placement recommendations
03
URL Structure
Taxonomy
What you receive
A clean URL taxonomy validated against keyword data, so every slug carries search intent from the moment the site launches.
NOW
timberfix.com.au/product-category/fasteners/cable-ties/zip-ties/
NEW
timberfix.com.au/fasteners/zip-ties/
What gets defined
- URL pattern for every page type: category, subcategory, product, blog, static
- Slug naming conventions validated against search volume
- Naming rules for future category additions
- Variable and attribute handling in product URLs
04
Product Description Framework
Content Matrix
What you receive
Not every page needs the same content treatment. A commodity fastener needs a clean spec table. A considered purchase like a chemical anchor system needs copy that explains application, substrate compatibility, and load rating. This framework defines what each page type requires, so copywriting effort and cost goes where it creates the most value.
| Page Type |
Short Description |
Long Description |
Spec Table |
| Category Landing (L1) |
No |
Yes — SEO copy |
No |
| Subcategory (L2) |
No |
Short intro |
No |
| Product Listing Card |
Yes — 1 to 2 lines |
No |
No |
| Product Page — commodity |
No |
No |
Yes — primary |
| Product Page — considered |
No |
Yes — full copy |
Yes |
| Brand / Supplier Page |
No |
Yes — range overview |
No |
Templates included
- Short description: character limit, keyword placement, format rules
- Long description: heading structure, word count range, CTA placement
- Spec table schema: attribute naming, unit formatting, required fields
- Variable product guidance: presenting 175-variable products without overwhelming the page or degrading WooCommerce performance
05
Keyword Research & Page Title Validation
SEO Foundation
What you receive
Search demand mapped to every node in the sitemap. Category names, navigation labels, page titles, and URL slugs are confirmed against real data before anything is locked in. This is what separates an IA that ranks from one that looks organised on a spreadsheet.
What gets validated
- Top-level category naming: does the current label match buyer language or miss search volume?
- Subcategory priority: which L2 pages justify a dedicated URL vs a filtered view
- Page title and H1 recommendations, per page
- URL slug validation: keyword in slug, no stop words, consistent format
- Gap identification: demand with no current page to capture it
- Competitor page analysis for highest-priority categories
How it connects to the rest
Keyword research runs in parallel with the sitemap and URL work, not after. Every decision in the IA is grounded in data before it's final. No retrofitting keyword strategy onto a structure that's already been handed to development.
The Outcome
A site that's built right the first time.
When this engagement is complete, the new Timberfix site has a validated blueprint: every page defined, every URL confirmed, every content requirement mapped. Development can build against it with no structural assumptions.
Zero structural rework post-launch
URL changes after launch cost rankings. Navigation changes after build cost development time. Both are eliminated when structure is locked before code is written.
SEO value from launch day
Keyword-validated URLs, page titles, and site structure mean the new site begins ranking before any content campaign or link building starts. The architecture itself carries weight.
Variable complexity resolved
The 175-variable problem is addressed at the architecture level. How products are grouped, attributed, and filtered is defined before any template is built, not discovered mid-development.
Built to scale
New categories, brand pages, trade portal integration, and content hubs plug into the existing structure without rebuilding it. The IA is designed for the business Timberfix is becoming, not just the range it carries today.
Built to hand off to your development partner. Every structural decision in this blueprint — sitemap, URL taxonomy, navigation hierarchy, description framework — is documented to the level of precision a WooCommerce developer can build against directly. The IA accounts for the 175-variable constraint at the architecture level, so your developer isn't solving that problem mid-build. Development itself is a separate engagement; this blueprint is what makes that engagement predictable.
Investment
$5,000 + GST
A fixed-fee engagement covering all six deliverables from discovery through to a completed, validated IA blueprint.
Six IA Deliverables
Discovery and catalogue briefing, sitemap, navigation architecture, URL structure, product description framework, and keyword research, produced as a connected set and delivered as a single blueprint document.
2-Week Delivery
The completed blueprint is delivered within two weeks of kickoff. Discovery session confirmed, research runs in parallel, and all six deliverables are packaged for handover by the end of week two.
Milestone Check-ins
Structured review points at key stages so Timberfix can validate direction before work progresses. No surprises at final delivery.
Build-ready Handover
A complete blueprint packaged for handover to development: every structural decision documented, validated, and ready to build against.
What We Need From Timberfix
Good work requires a consistent feedback loop.
We can validate the architecture against search data and technical constraints, but product knowledge lives inside Timberfix. Questions will come up. That's expected. What matters is that answers come back promptly so the engagement stays on track.
Required
An Internal Point of Contact
One person at Timberfix who can answer product questions, validate category logic, and access ERP or stock system data when needed. This doesn't need to be a full-time commitment, but it does need to be a real one.
Required
Timely Responses
When we raise questions during the engagement, we need answers within a reasonable timeframe to avoid blocking progress. We'll flag what's urgent and what can wait, but a feedback loop that goes quiet slows everything down.
We will have validated all the major components before questions arise, but no blueprint process is entirely question-free. Product ranges have edge cases. Categories have internal nuance that data alone doesn't surface. Designating someone internally who can speak to the product catalogue and access system data is the single most important thing Timberfix can do to make this engagement run smoothly.