Acme Insights

Headline describes a category, not an outcome

Lead with the outcome and the buyer in under ten words, for example “Forecast revenue you can defend in the board meeting.” Move “AI-native” and integration claims to the subheading. A/B test two outcome-led variants against the current headline.

Feature section lists capabilities, not results

Rewrite each card as a result with a number where possible, for example “Catch pipeline risk two weeks earlier” instead of “Anomaly detection”.

First session lands on an empty dashboard

Replace the empty home with a three-step setup checklist (connect a source, pick a template dashboard, invite a teammate) with progress, and load a sample dataset so every panel shows a realistic preview until real data arrives.

Sign-up form asks for eight fields before any value

Reduce to work email and password, or Google sign-in. Collect role and company size inside the product after the first dashboard loads. Rename the button to “Start 14-day trial”.

Four equal-weight actions compete in the hero

Keep one primary button (“Start free trial”) and one secondary text link (“Book a demo”). Remove “Watch video” from the hero and embed the video lower on the page. Use a single accent color for the primary action site-wide.

Primary action falls below the fold on mobile

Shorten the mobile headline, hide the long subheading below 640px, and add a sticky bottom bar with the single primary action.

No customer proof anywhere on the page

Add a logo strip directly below the hero and one quantified customer outcome (metric, name, role, company) next to the primary call to action. Turn the “Built for scale” band into a proof section with real numbers.

Security posture is invisible for a data platform

Add a security band with compliance status, encryption and data residency, linking to a dedicated trust page.

Fix: AI crawlers allowed

Unless blocking is a deliberate policy, replace the blocking groups in robots.txt with an explicit allow for each crawler, e.g. "User-agent: GPTBot / User-agent: CCBot / Allow: / / Disallow: /app/" (keep private app paths disallowed). Re-test with each vendor's robots checker, then watch server logs for the crawlers returning within a few days.

Fix: Question-and-answer content

Add an FAQ section to the home, pricing and product pages with 5-8 real buyer questions as H2/H3 headings ("How long does setup take?", "How is pricing calculated?") and 40-60 word direct answers, and mark it up with FAQPage JSON-LD.

Fix: Answer-ready summary

Directly under the H1, add a 40-80 word paragraph that reads as a definition: "Acme Insights is a revenue analytics platform for B2B SaaS revenue teams that forecasts pipeline and flags risk two weeks earlier. It connects CRM, billing and product data in minutes, and is used by <proof>." Assistants lift this kind of sentence verbatim.

Fix: Author and publisher signals

Show a byline with the author's name, role and a link to their profile page, and add Article JSON-LD with "author" (Person with name, url, sameAs LinkedIn) and "publisher" (your Organization). Expertise signals make content more likely to be cited.

Fix: Citable facts and numbers

Add 3-5 sourced facts per key page: customer count, a quantified customer result ("cut forecast error by 32% at Northwind"), setup time, number of integrations and starting price. Put each in its own short sentence so it can be quoted on its own.

Fix: llms.txt

Publish /llms.txt as Markdown: "# Acme Insights" on the first line, a "> one-sentence summary of what it is and who it is for", a short paragraph on key facts (category, pricing model, integrations), then "## Product", "## Pricing", "## Docs" and "## Customers" sections, each a list of "- [Page title](absolute URL): one-line description". Keep it under 100 lines and update it with each launch.

Fix: Freshness signals

Add "datePublished" and "dateModified" to each page's JSON-LD, show "Updated <month year>" on docs and articles, and send an accurate Last-Modified header from the server or CDN.

Thirteen navigation items before the first insight

Group navigation into Analyze (Dashboards, Explore, Alerts), Build (Metrics, Datasets, Models) and Admin. Collapse the Build and Admin groups for new accounts.

Toolbar offers four actions with no clear primary

On empty accounts show only “Connect a data source”. Reveal Export and Share once a dashboard exists.

Hero copy is too dense to scan

Cut the subheading to one sentence of under 20 words that supports the headline outcome. Move the capability list into the features section.

Navigation exposes nine top-level choices and no pricing

Reduce to Product, Customers, Pricing and Resources. Move Partners, Company, Careers and Blog into the footer. Show at least the starting price or plan structure.

Fix: Meta description present

Add a 70-160 character meta description to each page that states who it is for and the outcome it delivers.

Fix: Unique page titles

Write a distinct title for each page so search engines and AI assistants can tell them apart.

Fix: Title length (30-60 characters)

Rewrite titles to 30-60 characters: the page's specific topic or outcome first, then the brand name.

Fix: Description length (70-160 characters)

Keep descriptions between 70 and 160 characters so they are not truncated or padded in results.

Fix: Open Graph sharing tags

Add og:title, og:description and a 1200x630 og:image to every page (and twitter:card).

Fix: Fast page response

Cache HTML at the edge (CDN), reduce server work per request and pre-render marketing pages statically.

Fix: Lean HTML

Move inline data, SVG sprites and scripts out of the HTML and lazy-load below-the-fold content.

Fix: Structured data (JSON-LD)

Add a <script type="application/ld+json"> block to the home page with an @graph of: Organization (name, url, logo, sameAs), WebSite (name, url) and SoftwareApplication (name, applicationCategory "BusinessApplication", operatingSystem "Web", offers with price and priceCurrency, aggregateRating if you have reviews). Validate with Google's Rich Results Test and the Schema.org validator.

Fix: Organization or product schema

Add Organization (name, logo, sameAs social profiles) and WebSite schema site-wide, plus SoftwareApplication or Product schema on product and pricing pages.

Fix: Brand entity defined

Add site-wide Organization JSON-LD with "name", "url", "logo" (absolute URL to a square PNG), "description" and "sameAs" listing LinkedIn, Crunchbase, G2, GitHub and X profile URLs. Use the exact same company name everywhere.

Fix: Image alt text

Add descriptive alt text to meaningful images (product screenshots, diagrams, logos) and alt="" to purely decorative ones.

Fix: One H1 per page

Use exactly one H1 per page that states the page's main topic; demote other headings to H2.

Fix: Substantial page content

Expand key pages with specific, answer-style copy: who it is for, the problem, how it works, proof and FAQs.

Fix: Logical heading outline

Structure each page as H1 (page topic), H2 per section phrased as the question or benefit it covers, and H3 for details, without skipping levels. AI systems split pages into passages along these headings.