Two-thirds of ghosteye.ai's 415 indexed pages are glossary definitions: 274 terms in nine topics, from Help-desk & recovery to Email & fraud. Every blog post ends with "Request Your Free Campaign", but the glossary pages checked (the index, "Vishing", "Access token" and "Access review") have no link to the free campaign, the platform or the booking page. A security lead who arrives from search on "help-desk vishing" or "MFA fatigue" reads a careful definition and can only leave through a related post or an outside source. The site is not losing them to speed: it scores 100 and real visitors pass Core Web Vitals. The missing piece is the next step.
First action
Write the nine topic lines and add the block to the glossary template, keyed on the topic field.
How to measure it
Glossary-to-free-campaign click rate
- Now
- –
- Target
- 1.5% of glossary visits
- By
- 60 days
Steps
Check topic tags
Confirm each of the 274 terms has one of the nine topics, and tag any that do not.
Founding Head of Marketing 1 day
Write nine lines
One question and one offer per topic, in the plain voice of the existing pages, with no fear statistics.
Founding Head of Marketing 1 day
Build the block
One component in the glossary template, after the definition, linking to /book-demo/ with the term as a URL parameter.
Software Engineer, Full Stack 1 day
Pass the term to the booking
Carry the parameter into the calendar booking so the scoping call opens with the term the visitor read.
Software Engineer, Full Stack 2 hours
Pick a fallback post
For each topic, choose the best scenario post for readers who are not ready to book.
Founding Head of Marketing 1 day
Measure by topic
Clicks and bookings by topic each week, with the blog's closing button as the baseline.
Founding Head of Marketing weekly
Rewrite the weakest
After 30 days, rewrite the two lowest-performing topic lines.
Founding Head of Marketing 30 days
Why it works
Add one block to the glossary template, chosen by the topic each term already carries. Nine short variants, one per topic, each asking the question that term raises and offering the free campaign as a scoped test of it. Example for Help-desk & recovery: "Would your help desk reset this account for the wrong caller? Your first campaign tests one recovery route, scoped and stopped where you choose." Place it after the definition and before Sources. Link to /book-demo/ with the term in the URL, so the scoping call starts from the attack the reader just studied. For topics where a test is a less natural ask (Data & incident response, for example), lead with the best scenario post and keep the button second.
Glossary readers are looking up the exact attacks GhostEye simulates. Offering a scoped test of that attack at the moment they understand it turns reference traffic into scoping calls. Every term already carries one of nine topics, so one template component with nine lines covers all 274 pages.
Ready to use
CopyNine glossary call-to-action lines, one per topic
Help-desk & recovery: Would your help desk reset this account for the wrong caller? Your first campaign tests one recovery route, scoped and stopped where you choose. Social engineering: See whether this works on your team, by voice, SMS, email or chat. Your first campaign is on us. Tokens & sessions: If someone handed over a session, what could it reach? Test it on designated accounts in your first campaign. Identity controls: Find out whether this control holds when someone asks politely. Scope a free first campaign. Security testing: Run this test against your people and controls, with evidence for the control owner. Your first campaign is on us. Email & fraud: Would a payment or supplier change get through? Test one approval route in a free campaign. Devices & software: Would someone install this because 'IT' asked? Find out in your first campaign. Applications & supply chain: Test whether a convincing request can open this door. Scope your first campaign. Data & incident response: Read the scenario first, then test whether your team would spot it. Your first campaign is on us.
Risks and how to handle them
Reference pages start to feel like sales pages
One line and one button below the definition; Sources and related terms stay as they are.
Glossary traffic is mostly students or researchers
Judge by bookings, not clicks; if quality is low, offer the matching worksheet instead of the call.
Evidence
- Your websiteGlossary (checked November 9, 2026: the index and the "Vishing", "Access token" and "Access review" pages): 400-500-word definitions with sources, related terms and "See it in practice" links to blog posts, filed under nine topics (Help-desk & recovery, Social engineering, Tokens & sessions, Identity controls, Security testing, Email & fraud, Devices & software, Applications & supply chain, Data & incident response); none of these pages links to the free campaign, the platform or the booking page, and none shows a date.Source
- Your websiteSitemap (415 URLs, checked November 9, 2026): 274 glossary terms plus an index, 93 blog posts, 12 event pages, worksheet and resource listings, and core pages (platform, integrations, why-ghosteye, company, book-demo, contact, information-security); no pricing, comparison, industry, solution or case-study pages.Source
- Your websiteBlog post "Run an Account Recovery Tabletop: A Facilitator's Guide" (published August 21, 2026, by the CEO): a 90-minute agenda, four CSV facilitator files, links to the help-desk verification guide, and a closing section "Put a tabletop finding to the test." with the "Request Your Free Campaign" button; its structured data carries a dateModified of 2026-10-15 that readers do not see.Source
- PageSpeedGoogle PageSpeed (November 9, 2026): mobile and desktop performance 100, accessibility 96 (one colour-contrast issue), SEO 100; real visitors pass Core Web Vitals (field LCP 1.5 s, CLS 0); homepage weight 126 KB.Source