Semble's site already pre-renders six pages: the Bluebeam, Fieldwire and System Surveyor comparisons and the three trade pages return their full text to any reader. The other pages do not. The homepage, /pricing, /faq, /demo, /blog, all six product pages, the Togal and Bobyard comparisons and every blog post checked return only a page title until JavaScript runs. That includes "Fieldwire vs Semble (2026)" and "System Surveyor vs Semble (2026)". AI assistants and link previews usually do not run JavaScript, and Google indexes such pages late and unreliably. So most of what Semble writes for integrators is invisible to the places integrators research tools.
First action
Find why /compare/fieldwire is pre-rendered and /compare/togal is not, and use the same route setting for every sitemap URL.
How to measure it
Readable and indexed sitemap URLs
- Now
- –
- Target
- 29 of 29 readable; 25+ indexed
- By
- 30 days
Steps
List the gaps
Fetch all 29 sitemap URLs without JavaScript and mark which return only a title.
Co-founder (product and engineering) 1 hour
Copy the working setup
Use the pre-render or static-generation setting the comparison and trade pages use for every marketing route.
Co-founder (product and engineering) 1 day
Sales pages first
Homepage, pricing, demo and the six product pages, with real H1s, copy and internal links.
Co-founder (product and engineering) 1 day
Then the blog
All nine posts with a visible date, author and links to the matching comparison page.
Co-founder (product and engineering) 1 day
Fix the sitemap
Add lastmod dates and resubmit in Search Console and Bing Webmaster Tools.
Co-founder (product and engineering) 1 hour
Verify
URL Inspection on ten key pages, and a plain fetch of each to confirm body text.
Co-founder (go-to-market) 2 days
Guard against regressions
Add a build check that fails if any sitemap URL renders without its H1.
Co-founder (product and engineering) half a day
Measure
Indexed pages, impressions and demo bookings from organic search, monthly.
Co-founder (go-to-market) monthly
Why it works
Use the same pre-rendering the comparison pages already get for every URL in the sitemap, so each one ships its headline, body copy, tables and links as HTML. Start with the pages that sell: homepage, pricing, demo, the six product pages, the Togal and Bobyard comparisons and the nine blog posts. Add a visible date and author to each post and lastmod dates to the sitemap. Then check each URL with a plain fetch and Google's URL Inspection, and track indexed pages and impressions in Search Console.
The content already exists and the build already pre-renders some pages, so this is a configuration fix rather than new writing. Every blog post and product page becomes something Google can rank and AI assistants can quote when an integrator asks for an alternative to Bluebeam, Fieldwire or System Surveyor. Pages that are invisible today start pulling in visitors.
Ready to use
ChecklistReadable-site checklist
[ ] Homepage returns H1 and body copy without JavaScript [ ] /pricing returns plan names and prices as text [ ] /demo, /faq, /blog return text [ ] Six /product pages return text [ ] /compare/togal and /compare/bobyard return text like the other three [ ] Nine blog posts return text, date and author [ ] Sitemap has lastmod dates [ ] Build check fails on title-only pages [ ] Search Console resubmitted
Risks and how to handle them
Pre-rendered pages drift from the interactive versions
Render both from the same components and keep the build check.
Interactive demos (canvas, booking widget) do not pre-render
Render the text and a static image server-side; load the interactive part after.
Evidence
- Your websiteRendering check (November 9, 2026, homepage fetched twice): the homepage, /pricing, /faq, /demo, /blog, all six /product pages, /compare/togal, /compare/bobyard and every blog post opened (including "Fieldwire vs Semble (2026)", "System Surveyor vs Semble (2026)" and "What AI Can Actually Do for an Integrator Today") return only a page title and no body text to a reader that does not run JavaScript. /compare/bluebeam, /compare/fieldwire, /compare/system-surveyor, /fire-alarm-design-software, /security-system-design-software and /blueprint-markup-software return their full text.Source
- Your websiteSitemap: 29 URLs with no lastmod dates: 9 blog posts, 6 product pages (Takeoff, Design, Materials, Versions, Field, Reports and sharing), 5 comparison pages (Togal, Bobyard, Bluebeam, Fieldwire, System Surveyor), 3 trade landing pages (security system design, fire alarm design, blueprint markup), pricing, demo, FAQ, privacy and terms. No customer stories, integrations, about or careers pages; /llms.txt returns 404. Product page titles include "Bills of materials from your drawings" and "PDF reports and read-only share links".Source
- Search checkWeb searches on November 9, 2026 for Semble AI pricing returned only similarly named products (mainly Sembly AI, a meeting-notes tool, plus Resemble AI and Assembly) and no Semble price. The pricing page serves no plan text to readers that do not run JavaScript; our earlier crawl recorded a subscription starting at $29 with no free tier or trial.Source