Twelve of the 18 URLs in Allus's sitemap are query-string versions of three templates. The HTML the server sends for /model-detail?model=allusedge and ?model=allusflow is titled "AllusONE — Industrial Perception & Reasoning" and never names AllusEdge or AllusFlow. The safety and production-process solution pages are both titled "Operational Knowledge & Guidance". The automotive and FMCG pages are both titled "Industries — Industrial Intelligence by Sector", with the hero "Industrial intelligence for {{ word }}" and no mention of their sector. The homepage HTML has the same gaps ("{{ heroSubline }}", FAQ "{{ q.q }}"). Browsers fill these in with JavaScript, but anything that reads the raw HTML does not: many AI assistant crawlers, link previews in email, Slack and Teams, and search engines before they render the page. A plant manager who forwards the AllusEdge link sends a preview titled AllusONE, and search engines may fold 12 pages into three.
First action
View source on /model-detail?model=allusedge and list every field each template fills in with JavaScript.
How to measure it
Distinct indexed template pages
- Now
- –
- Target
- 12 of 12, plus organic entrances to these pages
- By
- 60 days
Steps
Map the URLs
Old query URL to new path for all 12 pages.
Founder/CTO 2 hours
Prerender
Generate static HTML per page at build, with the template data filled in.
Founding AI Agent Engineer 3 days
Write unique heads
Title, meta description, H1 and Open Graph per model, solution and industry.
Founder/CEO 1 day
Redirect
301 each query URL to its new path; self-canonical on every page.
Founder/CTO 2 hours
Update the sitemap
New paths, real last-modified dates, internal links.
Founder/CTO 1 hour
Check without JavaScript
Fetch each page with JavaScript off and test link previews in Slack and Teams.
Founder/COO 2 hours
Submit and watch
Search Console sitemap submission and the indexing report.
Founder/CTO 4 weeks
Why it works
Move each page to a clean path (/models/allusedge, /solutions/industrial-safety, /industries/automotive) and prerender it at build time, so the HTML already holds a unique title, meta description, H1, body copy, FAQ and customer-story link. The site is React on Vercel, so the change is a build step, not a rebuild. Add self-canonicals, 301 the old query URLs to the new paths, update the sitemap and internal links, and add Open Graph tags per page. Then each model, task and sector page can match the searches it serves, such as "edge vision model for factories", "AI visual inspection automotive" and "food and beverage line monitoring", and shared links show the right product.
Industrial buyers research quietly and forward links internally before they ever fill in a form. Pages that read correctly without JavaScript are found by search engines and AI assistants and preview correctly when shared, and the work is mostly done once, in the build.
Ready to use
ChecklistTemplate page fix list
[ ] /model-detail?model=allusone -> /models/allusone [ ] /model-detail?model=allusflow -> /models/allusflow [ ] /model-detail?model=allusedge -> /models/allusedge [ ] 4 solution pages -> /solutions/<slug> [ ] 5 industry pages -> /industries/<slug> [ ] Unique <title>, meta description, H1, Open Graph per page [ ] Body copy, FAQ and story link in the served HTML [ ] Self-canonical + 301 from each old URL [ ] Sitemap with new paths [ ] Check with JavaScript off and in Slack/Teams previews
Risks and how to handle them
Redirects lose any existing ranking
Use one-to-one 301s and keep the old URLs redirecting permanently.
Prerendered and live content drift apart
Generate both from the same data file at build.
Evidence
- Your websiteModel, solution and industry pages (checked November 9, 2026): the HTML served for /model-detail?model=allusedge and ?model=allusflow is titled "AllusONE — Industrial Perception & Reasoning | Allus AI" and never names AllusEdge or AllusFlow; ?solution=industrial-safety-site-intelligence and ?solution=production-process-intelligence are both titled "Operational Knowledge & Guidance | Allus AI"; ?industry=automotive and ?industry=fmcg are both titled "Industries — Industrial Intelligence by Sector | Allus AI", with the hero "Industrial intelligence for {{ word }}" and neither naming its sector.Source
- Your websiteSitemap (19 URLs, last modified September 2, 2026): 12 are query-string versions of three templates: /model-detail?model= (allusone, allusflow, allusedge), /solution?solution= (operational knowledge, production process, equipment and asset, industrial safety) and /industry?industry= (electronics assembly, FMCG, food and beverage, advanced materials, automotive). There are no blog, customer-story, careers, pricing or comparison URLs.Source
- Your websiteHomepage (checked November 9, 2026): the HTML the server sends shows "Industrial Intelligence" followed by "{{ heroSubline }}" and "See, understand and act on {{ rotWord }}"; the solutions, industries, "What sets it apart" and FAQ ("Before you ask: Hardware, data, decisions.") sections are placeholders such as "{{ q.q }}" and "{{ q.a }}"; CTAs "Request a Demo", "Explore the Models" and "Start a Pilot"; "SOC 2 Type II" and "A3 Member" badges with a Trust Center link; "Backed by" Y Combinator and NVIDIA Inception Program; "Read the customer stories"; "Cupertino · Atlanta".Source
- ResearchSite changes since November 15, 2025 (programmable.info): Webflow and Calendly removed, React added. The headline went from "Vision Foundation Model for Manufacturing" to "Industrial Intelligence {{ heroSubline }}". No pricing page, blog, newsletter or case-study pages were detected, and the site links to no LinkedIn, X or YouTube profiles.Source