Initial SEO Review · 2 October 2026 · Prepared by SearchFlex
9,019 product pages, a fast stable platform, and structured data already in the CMS — a few targeted changes will unlock the full catalogue for search engines and AI discovery tools.
This review is based on a full XML sitemap crawl on 2 October 2026, a manual review of rendered pages, and publicly available search data. Access to Google Search Console and GA4 is needed to confirm indexing and traffic detail.
Catalogue composition — 9,019 URLs
Source: XML sitemap crawl, 2 October 2026
The foundations are solid. The work ahead is about surfacing what the platform already has — not rebuilding it.
Every URL in the sitemap returns a successful HTTPS response with no redirect chains or server errors. Median server response time: 0.31 seconds. An excellent technical foundation.
The sitemap covers the full catalogue: 7,614 tyre, 933 wheel, and 444 accessory pages. Search engines have a complete map of the estate — the challenge is making those pages readable on first request.
Brand, pattern, size, load index, speed rating, and tyre type are already held for every product. Page titles, headings, and structured data can be generated automatically from the existing data — no manual entry required.
23 tyre brands and around 30 wheel brands, including YHI’s own Advanti Racing range, plus the Kustomizor wheel visualiser. This brand depth is a significant organic search asset waiting to be fully indexed.
The site’s biggest SEO issue is a single architectural pattern: pages are built in the browser with JavaScript. Without executing that JavaScript, a crawler sees almost nothing.
Page load waterfall — what a user (and crawler) experiences
Widths are illustrative of relative timing. Server-side rendering eliminates the JS stage entirely — reducing content-first-visible to near server-response time.
Eight opportunities identified from the initial crawl, in priority order. Each priority level is explained below. A full audit with Search Console access will confirm ranking and commercial impact.
Pages are built in the browser with JavaScript. The HTML returned on first request contains no title, text, or links. To a crawler without JavaScript, all 9,019 sitemap pages appear as just 14 distinct pages. Google can render JavaScript, but this adds a second processing stage and delays indexing.
Product titles follow the format “YHI | PILOT SPORT 4S” — no brand, no size. The homepage title is “YHI | Dashboard”. Every page uses the framework’s default meta description, meaning Google rewrites them from page content (which is often empty).
Category pages and the tyre/wheel finders do not link to product pages with standard HTML links, so the XML sitemap is the only route for search engines to find the 8,991 product pages. There are no brand or range landing pages anywhere on the site.
Each tyre and wheel size has its own URL, so 6,830 of 8,547 tyre and wheel URLs share a product name with at least one other page. For example, the Michelin Pilot Sport 4S has 171 separate pages — one per size — each with near-identical content. Most URLs also omit brand and size from the URL slug.
Pages reviewed have no H1 heading, no canonical tag, no structured data, and no Open Graph tags. This means search engines must infer the page’s topic without the standard signals, and product pages display poorly when shared on social or in AI summaries.
Former wheeldemon.com.au URLs redirect to the yhi.com.au homepage, and some former Wheel Demon product pages still appear in search results. This means the rankings and backlinks built up on the previous domain are not yet benefiting the most relevant YHI pages.
Login and password recovery pages on cms.yhi.com.au appear in search results. Non-existent product URLs return 200 (OK) rather than 404 (Not Found). The robots.txt is the CMS default pointing to the CMS subdomain, and the sitemap gives every URL the same last-modified date.
Product details load only after a sequence of account checks, even for visitors who are not logged in. In a single test, content first appeared after about 4.3 seconds. Five recommended security headers are not set: HSTS, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
The size-per-URL structure means thousands of nearly identical pages compete with each other in search. Consolidation creates fewer, stronger pages that can rank for brand and pattern searches.
Pilot Sport 4S count from sitemap crawl. Typical pattern counts are illustrative of the structural issue, not measured.
Three parallel tracks to move from this initial review to a measurable improvement in organic visibility and trade account enquiries.
Changes that can be made without restructuring the site, agreed and shipped in the first sprint.
Confirm how Google crawls, renders, and indexes the site. Identify which pages and searches drive trade account registrations and enquiries. Prioritise structural work by measured commercial impact.
The changes with the highest long-term impact, sequenced by complexity and likely commercial return from the audit findings.
To confirm current indexing status and prioritise by revenue impact, three access points are needed before the full audit can begin.
Confirms how Google indexes the site today, which pages are crawled vs. rendered, and which queries drive impressions. Essential for the crawl investigation.
Shows which organic pages and searches convert to trade account registrations and enquiries — needed to prioritise by commercial impact rather than traffic volume alone.
Access to the Next.js codebase or staging environment to understand the current rendering setup and investigate why the crawler could not read page content.
The technical foundations are strong. With Search Console access and a full audit, we can confirm exactly which of these opportunities to prioritise and what traffic and enquiry uplift to expect from each.
Get the full audit →