Petra's best proof is its customer stories: 27x AI-referred traffic for Novig, 65% of Fractional Jobs' inbounds from AI search, 90% of Josh Linkner's inbound leads. But every story page tells search engines and AI assistants the same thing as the homepage ("Petra Labs is your end-to-end AEO partner...") and has no H1, so the numbers never reach a search result, a link preview or an assistant's summary. The same template problem gives the newsletter and terms pages the title "Privacy Policy". The new Growth Engineer is hired to educate a market and build pipeline beyond referrals; these pages are the proof that work will point to.
First action
Rewrite the Novig story's title, description and heading today.
How to measure it
Search clicks and assistant citations to /customers pages
- Now
- –
- Target
- 3x
- By
- 90 days
Steps
List the pages
Four stories, eight event pages, /newsletter, /terms, /events.
Growth Engineer 1 hour
Write the fields
Result-first titles and descriptions; one H1 each.
Growth Engineer 1 day
Fix the template
Per-page fields in the Framer CMS collection, not the shared default.
Software Engineer 1 day
Add markup
Article schema with customer, date and figures.
Software Engineer 1 day
Baseline assistants
Run the case-study prompts in Petra's own platform.
Data Scientist 2 days
Request recrawl
Search Console for the changed URLs.
Growth Engineer 1 hour
Re-measure
Citations and clicks after 30 and 60 days.
Data Scientist monthly
Why it works
Write a unique title and meta description for each story that leads with its result and the buyer type (for example "How Novig grew AI-referred traffic 27x in six months | Petra Labs"), add one H1 per page, and add Article markup with the customer, date and key figures. Apply the same fix to the eight event pages and to /newsletter, /terms and /events. Then ask the assistants Petra tracks "Which AEO agencies have case studies?" and "Who helped Novig with AI search?" and record whether the stories are cited.
Answer engines lift short factual statements from titles, descriptions and headings. A story that states its number in those fields can be quoted; one that repeats the homepage line cannot. For a company that sells AI visibility, its own proof pages are also a live demo.
Ready to use
ChecklistStory page fix list
[ ] Title leads with the result and the customer [ ] Meta description: problem, what Petra did, number, time span [ ] One H1 per page [ ] Article schema with customer, date and key figures [ ] /newsletter and /terms titles and descriptions corrected [ ] /events and the eight event pages given their own descriptions [ ] Story prompts added to Petra's own tracking
Risks and how to handle them
Customers object to new headline wording
Use the figures already approved in each published story.
A template change breaks other CMS pages
Check every page in the collection after publishing.
Evidence
- Your websitePage metadata check of every sitemap URL (43 URLs, October 22, 2026): all four customer stories (Zapier, Novig, Fractional Jobs, Josh Linkner) and all eight event and replay pages reuse the homepage meta description "Petra Labs is your end-to-end AEO partner, from measurement, to execution, to attribution" and have no H1 tag; their titles end in "- Petra Labs: Your AI Search Team". /newsletter and /terms carry the title "Privacy Policy | Petra Labs" and the privacy policy's description; /events uses the homepage title and description. The 22 /intelligence articles, by contrast, each have their own title, description and one H1.Source
- Your websiteCustomer stories: Novig, "27x AI-referred site traffic in six months", visibility "21%, up from 0%" across "1,500+ prompts"; Fractional Jobs, "+53%" AI-referred traffic in three weeks and "65% of all inbounds come from AI search"; Josh Linkner, "5x AI-referred site traffic in under 2 months", "90% of inbound leads now coming from AI search", with the annual engagement "paid back several times over"; Zapier, "It became clear to Zapier early on that Petra was more than just an analytics dashboard" (no headline numbers).Source
- HiringGrowth Engineer (New York, posted September 1, 2026): "Today, the vast majority of our pipeline comes from inbounds and referrals from success with our existing customers." The hire builds "the GTM engine from the ground up": "generate qualified enterprise leads, create content that educates a market that barely knows this category exists, and run experiments across channels", designs "targeted outbound campaigns tailored to marketing leaders, VPs, and CMOs", and must "write something a CMO would actually want to read". "Petra isn't SaaS. Our deals are meaningful, the sales process can take time."Source
- HiringStrategic Account Executive (posted August 26, 2026): "This is our first Account Executive hire." Many prospects "are still figuring out what that means for their business"; the AE must be comfortable "selling a newer product or category where the buyer may not already have a dedicated budget", will "Build and improve decks, proposals, case studies, and other sales materials" and help decide "which companies to target, what messaging works, how we qualify opportunities".Source