メニュー
Use when asked to audit a site's SEO, check AEO or answer-engine readiness, diagnose why a page is not ranking or not being cited by AI, verify structured data, or run pre-deploy discoverability checks on built HTML.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/bemoshiur/OmniRank --skill auditコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Draft a daily LinkedIn post for S M Moshiur Rahman about business development, grounded in a real problem he hit that day and real numbers from OmniRank. Use when he says "linkedin post", "today's post", "draft a post", or describes friction he wants written up.
Use when asked to generate or fix llms.txt, llms-full.txt or facts.json, make a site citable or ingestible by ChatGPT, Claude, Perplexity or Gemini, or publish machine-readable ground truth for AI crawlers.
SOC 職業分類に基づく
SKILL.md を表示中
| name | audit |
| description | Use when asked to audit a site's SEO, check AEO or answer-engine readiness, diagnose why a page is not ranking or not being cited by AI, verify structured data, or run pre-deploy discoverability checks on built HTML. |
Score a site across four layers — SEO, AEO, GEO, and crawl hygiene — and produce a prioritised, actionable fix list.
Anything shaped like "is this site discoverable?" Ranking complaints, schema questions, pre-deploy verification, or "why doesn't ChatGPT cite us?"
llms.txt / facts.json — that is geo-artifacts.aeo-onpage (planned, not in v0.1.0).indexing (planned, not in v0.1.0).offsite-entity (planned, not in v0.1.0).Audit only diagnoses. It never edits the site.
omnirank fix shows the diff it would apply for the four mechanical findings and
writes nothing — there is no --write flag. Run it to answer "which file is
wrong?", then hand the diff to a human.
# Zero-config, any live site
python3 -m omnirank.cli audit https://example.com
# Configured repo, CI-ready
python3 -m omnirank.cli audit --config omnirank.config.json --fail-on h1 canonical schema
Exit codes: 0 clean, 1 a configured gate failed, 2 usage or config error.
The JSON report lands in .omnirank/reports/<date>-audit.json.
--fail-on takes gate names (h1, canonical, title-length, llms-txt,
facts-json, schema, ...), not finding ids — see references/gates.md for the
full name list and how ids relate to them.
Work findings in severity order — every error before any warning. Each finding carries
observed, expected, and fix; quote the fix when proposing the change, and cite the
id so it can be tracked across runs.
Scores are 100 - 10×errors - 3×warnings per layer, floored at zero. A layer with no
findings is absent from the score map rather than scored 100 — never report a score for a
layer whose gates did not run.
.next/server/app/*.html or a raw curl, never a browser inspector.See references/gates.md for what every gate checks and why, and
references/crawl-hygiene.md for the 404/410/redirect policy.