DRAFT NOTES — DELETE BEFORE PUBLISHING
- Intended URL: /longtail-forge/ — top level, parent for demo, roadmap, use-cases, and changelog.
- MAJOR GAP: I have no information about what Longtail Forge does — there’s nothing about it anywhere on the existing site, and I’m not going to invent a product description. Every substantive claim on these five pages has to come from you. What’s here is the structure, the section order, and notes on what each section needs to accomplish.
- Meta title: Longtail Forge — [ONE-LINE PRODUCT DESCRIPTION] | Raymond Tec
- Meta description: [WRITE ONCE THE PRODUCT IS DEFINED — 150 chars, must say what it does and who it’s for. Don’t publish this page with a placeholder description; a vague meta description on a product page kills click-through.]
- Internal links to add: /longtail-forge/demo/, /longtail-forge/use-cases/, /longtail-forge/roadmap/, /longtail-forge/changelog/, /work/longtail-forge/, /services/custom-app-development/
- CTA DECISION: the framework specifies “Request a Free Estimate” on service pages, but that’s the wrong CTA for a product. This page should convert to a trial, waitlist, or demo. The estimate CTA is included below as a secondary — swap the primary once you know what the product offers.
- Naming: “Longtail” suggests long-tail search, so readers will assume it’s an SEO or content tool. If it isn’t, the first sentence has to correct that assumption immediately.
[HEADLINE — what it does, in one sentence a stranger understands. Not a tagline. “Longtail Forge finds the search terms your competitors ignore and turns them into pages” is the shape; a phrase like “Forge your digital future” is not.]
[SUBHEAD — who it’s for and what it replaces. Two sentences.]
The problem it solves
[PLACEHOLDER — describe the situation the user is in before they have this tool. Concrete and specific. The reader should recognize themselves here or leave.]
How it works
[PLACEHOLDER — three or four steps, plainly stated. Screenshots do more than copy here. If it’s not ready to screenshot, it may not be ready for a public page.]
Who it’s for
[PLACEHOLDER — and equally, who it isn’t for. Naming the non-fit is unusual enough that it builds trust, and it cuts support load from users who’d have churned.]
Where it stands today
[PLACEHOLDER — current stage stated honestly: in development, private beta, open beta, generally available. Include what’s not built yet. Readers evaluating early software respect this and punish the opposite.]
Pricing
[PLACEHOLDER — or, if pricing isn’t set, say “pricing isn’t finalized” rather than omitting the section. An absent pricing section makes people assume it’s expensive.]
Built by Raymond Tec
Longtail Forge comes out of the same practice that does client development work. If you need something built for your own business rather than a product off the shelf, that’s a different conversation and a welcome one.
