{"id":95680,"plugin_id":"plugin_asdk_app_6ae7ba73a20c819194ad481a9bf41597","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-13T18:12:43.580Z","digest":"babcbb3db475510b82a31dbfb27e78ab3aabac10100f4473f2404cfd4a2d132e","against":null,"payload":{"description":"Route a live pet project through the atlas — take the reports of the existing SEO and GEO audits, merge them into one prioritised list, link the page that explains each item, and name three things to do this week. Use when the user says \"nobody finds my project\", \"where do I start with SEO\", \"прогони проект по атласу\", or pastes an SEO or AI-search audit of their site and asks what to fix first.","included_files":[],"name":"start","skill_md_contents":"---\nname: start\ndescription: Route a live pet project through the atlas — take the reports of the existing SEO and GEO audits, merge them into one prioritised list, link the page that explains each item, and name three things to do this week. Use when the user says \"nobody finds my project\", \"where do I start with SEO\", \"прогони проект по атласу\", or pastes an SEO or AI-search audit of their site and asks what to fix first.\n---\n\n# start\n\n**This skill runs no checks of its own.** It orders the output of two audits that already exist,\n`seo-audit` and `geo-audit`, against the atlas route. Every finding below comes from one of their\nreports. If you find yourself fetching `robots.txt` by hand, you have left this skill — stop and ask\nfor the report instead.\n\n## 1. Ask two questions\n\nAsk both before running anything, and wait for the answers:\n\n1. **The URL of the live site.** Not a staging host, not localhost. The audits read what search reads.\n2. **The language the audience searches in.** It decides which results pages matter and what language\n   the recommended pages are written in. It is not the language of the interface.\n\nIf the project has no public URL — it lives only in Telegram, in a store, or in an app — say so and go\nstraight to [search inside the platform](https://atlas.smolevich.com/distribution/in-platform-visibility/).\nThe audits below need a page to fetch.\n\n## 2. Get the two audit reports\n\n`seo-audit` and `geo-audit` are open-source skills maintained by other people. They run in a coding\nagent on the user's computer, not here. Ask the user to paste or upload the full output of both, run\non the URL from step 1. If either audit is available as a skill in this environment, run it on that\nURL instead of asking.\n\nIf a report is missing, **say so and stop**. Do not substitute your own checks — a hand-rolled audit is\na worse audit that looks like a real one. Do not try to install anything. Give the user the install\nlines to run in their own coding agent, and say who maintains each package:\n\n```bash\nnpx skills add -g coreyhaines31/marketingskills\nnpx skills add -g zubair-trabzada/geo-seo-claude\n```\n\n`seo-audit` comes from `coreyhaines31/marketingskills`, `geo-audit` from `zubair-trabzada/geo-seo-claude`.\nNeither is part of this plugin. Once the user has both reports, they bring them back here.\n\nThat is the whole answer when a report is missing. End it there: no questions about the site, no\n\"meanwhile\" tip, no list, no route. The closing line about tagging links in section 6 belongs to a\nfinished run, not to this one.\n\nWhat each tool is and where it comes from: <https://atlas.smolevich.com/tools/skills/>.\n\n## 3. Read them, in this order\n\n1. **`seo-audit`** first. Fetch, block, canonical, indexing, on-page, speed.\n2. **`geo-audit`** second. Crawler access, citability, schema, `llms.txt`, platform readiness.\n\nSEO first. Access and indexing decide whether anything else is even read. A citability score for a page\nno agent can fetch is a score of a document nobody has.\n\nCheck that both reports are for the URL from step 1. If they name another host, say so before merging.\n\nKeep both raw reports. You will cite lines out of them, not summarise them into adjectives.\n\n## 4. Merge into one list\n\nOne list, not two. Drop the composite scores — a score moves when anything moves and tells the reader\nnothing to do. Keep the individual findings.\n\nOrder by this rule, top down. The first rung that is broken outranks everything below it:\n\n1. **Fetchable** — the page returns body text to a plain client. Any crawler, search or AI, that gets\n   a 4xx, a 5xx, a challenge page or an empty body is on this rung, whatever produced it: a CDN or\n   WAF rule answering 403 to `ChatGPT-User` is a fetch failure, not a directive.\n2. **Allowed** — the page is fetched but tells the crawler to stay out: `robots.txt`, `noindex`,\n   `X-Robots-Tag`.\n3. **Indexed** — submitted, discovered, in the index.\n4. **Findable** — the pages answer phrases people actually type.\n5. **Quotable** — an assistant can lift a passage and attribute it.\n6. **Attributed** — you can say which link sent the person.\n\nDeduplicate across the two reports. Both audits flag crawler access; that is one row, not two.\n\nDrop anything the audits report that this project cannot act on this month. A finding nobody will do is\nnoise in the list.\n\n## 5. Link the page for every item\n\nEach row gets exactly one atlas link. Route by symptom:\n\n| Finding | Page |\n|---|---|\n| Not fetchable, blocked, `noindex`, wrong canonical, JS-only body | [Google does not see your site](https://atlas.smolevich.com/indexing/why-google-does-not-see-you/) |\n| Not submitted, no sitemap, stale URLs, only the home page indexed | [Submit and verify](https://atlas.smolevich.com/indexing/submit-and-verify/) |\n| AI crawler blocked, or a published `llms.txt` gone stale | [AI crawlers and llms.txt](https://atlas.smolevich.com/geo/llms-txt-and-crawlers/) |\n| Low citability, no JSON-LD, no `sameAs`, assistants cite competitors | [Why AI answers cite someone else](https://atlas.smolevich.com/geo/citable-pages/) |\n| No impressions, pages target phrases nobody types, pages compete | [What to write about](https://atlas.smolevich.com/content/keyword-clusters/) |\n| Thin page, no answer up top, no failures block, weak titles | [What a page is made of](https://atlas.smolevich.com/content/page-templates/) |\n| Page two everywhere, no external links, no mentions | [Where the first links come from](https://atlas.smolevich.com/distribution/catalogs/) |\n| The product lives in a messenger or a store | [Search inside the platform](https://atlas.smolevich.com/distribution/in-platform-visibility/) |\n| Cannot say which numbers to read, activation unnamed | [The numbers worth reading weekly](https://atlas.smolevich.com/analytics/what-to-measure/) |\n| Links untagged, everything reads as direct | [Where the user came from](https://atlas.smolevich.com/analytics/attribution/) |\n| It works and costs more than it earns | [What one user costs](https://atlas.smolevich.com/money/unit-economics/) |\n\nA finding with no page in this table still goes in the list, marked as having no atlas page yet. Do not\ninvent a URL to fill the column. It keeps its rung: a slow page is still **Findable** and sits above every\n**Quotable** row, not at the bottom because the link column is empty.\n\nOutput one markdown table: rank, finding, the audit line it came from, the page.\n\n## 6. Close with three things for this week\n\nExactly three. Not five, not a backlog.\n\n- Take them off the top of the merged list, highest broken rung first.\n- Each one is a thing a person finishes in an evening. \"Improve content\" is not one.\n- Each one names how you will know it worked — a command, a report, a number.\n\nAdd one line the author cannot get from an audit: **tag your outbound links today if they are not\ntagged.** Attribution is the only item on the route that cannot be reconstructed later, so an untagged\nweek is a week of arrivals nobody will ever classify. That is\n[attribution](https://atlas.smolevich.com/analytics/attribution/).\n\nThen point at the full route for what comes after this week:\n<https://atlas.smolevich.com/start/>.\n\n## Rules\n\n- Do not invent findings. Everything in the list traces to a line in one of the two reports.\n- Do not report a score as an outcome. Report what to change.\n- If an audit fails to run, say which one and why. A half audit presented as a whole one is the failure\n  mode this skill exists to avoid.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}