Step 1 of 6
Audit existing routes for SEO data
Identify every public route and create a source of truth for meta information
The project is a React SPA using react‑router. Assume source files live under src/pages or src/routes.
Scan the repository for all public route definitions (ignore admin or auth‑only paths). Generate a file named seoRoutes.json in the project root containing an array of objects, each with keys: path (string, starting with '/'), name (human readable), title (string placeholder, e.g., "My Page Title"), description (string placeholder, e.g., "A brief description."). Commit the file. Do not include any private routes.
Expected after this step
seoRoutes.json exists at project root and lists every public route with placeholder meta fields.
Should not happen
- ✕AI returns UI mockups or screenshots instead of real code.
- ✕Meta tags are added only client‑side, not present in server‑rendered HTML.
- ✕Generated sitemap contains placeholder URLs or misses routes.
- ✕robots.txt placed in wrong folder or contains incorrect content.
Verify before continuing
Do not move on until every check is true. The complete button stays locked until then.
Do not continue if…
- !AI returns UI mockups or screenshots instead of real code.
- !Meta tags are added only client‑side, not present in server‑rendered HTML.
- !Generated sitemap contains placeholder URLs or misses routes.
- !robots.txt placed in wrong folder or contains incorrect content.
- !Missing persistence: changes are described but not written to disk.
If the AI messes this up
Use this when the AI fakes progress or breaks the feature. It forces a real fix.
The AI did not create a real seoRoutes.json or omitted required keys. Re‑run the step and explicitly write a valid JSON file with the exact schema described, ensuring it is saved to the repository.