title-meta-rewriter
Skill7 starsChanged 5 months agoMITView on GitHub
Generate title and meta description alternatives from GSC query evidence and SERP intent. Use when Codex needs to improve organic CTR by rewriting page metadata.
In this repository22 other files it gives its agents.
- authority-mark-keyword-difficultySkill
- cannibalization-checkSkill
- client-report-writerSkill
- competitor-serp-monitorSkill
- content-decay-monitor-setupSkill
- content-moat-plannerSkill
- content-refresh-briefSkill
- exceed-quality-thresholdSkill
- internal-link-builderSkill
- keyword-opportunity-finderSkill
- keyword-plannerSkill
- live-search-console-dataSkill
- proposal-builderSkill
- refresh-vs-new-contentSkill
- schema-fix-writerSkill
- seo-content-briefSkill
- seo-growth-loopSkill
- seo-offer-architectSkill
- seo-priority-scoreSkill
- seo-strategySkill
- technical-seo-triageSkill
- traffic-decay-detectorSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Check the current SERP for competitor title patterns.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Title Meta Rewriter
Overview
Given a page URL and its GSC query performance, produce title and meta description alternatives that better match search intent and improve organic CTR. Uses actual query data to understand what users are searching for.
Inputs
- Page URL
- GSC query data for the page (queries driving impressions, CTR per query)
- Optional: current SERP titles from top-ranking competitors
Workflow
- Analyze GSC queries that drive impressions to the page.
- Identify the primary query and secondary queries.
- Check the current SERP for competitor title patterns.
- Evaluate the current title and meta description: does it match the dominant query intent?
- Generate 3-5 title alternatives that:
- Include the primary query or close variant
- Match the search intent (informational, commercial, etc.)
- Differentiate from competitor titles
- Stay within length limits (60 chars for title, 160 for meta)
- Generate 2-3 meta description alternatives.
- For each alternative, note the expected CTR impact.
Output
Title and meta description alternatives with CTR rationale and recommendation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.