For end users
seed-keywords
Hand-typed seed keywords plus AnswerThePublic-style question imports. Bootstrap the analysis when live traffic is thin, or supplement live data with topics it doesn’t yet capture.
Type: inbound (manual). Minimal app.
What it does
Two project-scoped tables and a single Settings page.
seed_keywords— 5 to 10 keywords you want analysis to focus on. Edited via the Project keywords page.answer_public_entries— AnswerThePublic-style question / preposition / comparison phrases tied to each seed. Imported via CSV from the seed-keywords Settings page. Used byweekly-analysisto match suggested titles to the exact phrasing real searchers use.
Seed keywords don’t fit the usual inbound-app shape — no external API to fetch, just user-typed rows. ATP is similar: there’s no public AnswerThePublic API, so it ships as a CSV-only import. The pattern generalises to any user-typed source.
How to use
Activate seed-keywords for the project from /brands/<slug>/projects/<code>/apps. The project sidebar then surfaces a Seed keywords group with a Settings entry.
- Add seed keywords: the Settings page links to the canonical Project keywords editor. Type 5–10 keywords there.
- Import ATP entries: Settings page → AnswerThePublic entries section. Export a Queries / Questions list from AnswerThePublic (or any tool that lists phrases per seed) as CSV and upload. If the export lacks a Seed column, type the seed in the fallback field. Tab values normalize to
questions / prepositions / comparisons / alphabeticals / related. Upserts on(project_id, seed_keyword, tab, text)ignore duplicates so re-imports are idempotent. A “Last N imports” disclosure lists recently-inserted rows so you can verify a fresh upload landed.
When to use
- New project with no GA4 / Search Console history yet.
- Existing project where the live data misses topics you want the analysis to consider.
- After a content-strategy pivot — feed Pectus the new angle by hand before traffic catches up.
Where it lives
pectusai/apps/seed-keywords/APP.md