Catalog / olioa.co.jp
65

SEO audit for olioa.co.jp

OLIOA｜Brand new tomorrow

other

Health 65/100 (fair) · 18 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

商いに関わる思いを実現する。OLIOA株式会社は、ブランディング・Web・写真・DTPを通じて、事業の物語を静かに、確かに育てるクリエイティブカンパニーです。

18
pages crawled
17
indexable pages
0
errors
58
warnings
137
notices
0
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Security 70 0 18 18
Canonical 72 0 17 0
Content 73 0 16 0
Duplicate 92 0 5 2
Budget 98 0 1 0
Indexability 98 0 1 0
Agent Readiness 100 0 0 17
Images 100 0 0 18
Links 100 0 0 1
Meta Description 100 0 0 2
Performance 100 0 0 18
Sitemap 100 0 0 1
Social 100 0 0 34
Structured Data 100 0 0 17
Titles 100 0 0 9
Findings

Warnings (7 rules)

warning Noindex page receives internal links (crawl-budget waste)

Rule budget.noindex_linked · Budget · 1 occurrence(s)

  • https://olioa.co.jp/privacy.html — this noindex page has 18 internal inlink(s) — Googlebot follows them, fetches the page, then drops it unindexed, spending crawl budget for no indexing benefit (and the links leak equity). Remove/redirect the links, or drop the noindex if the page should be indexed. Linked from: https://olioa.co.jp/, https://olioa.co.jp/company.html, https://olioa.co.jp/team.html.

warning Missing canonical tag

Rule canonical.missing · Canonical · 17 occurrence(s)

warning Thin content (low word count)

Rule content.thin · Content · 16 occurrence(s)

warning Homepage duplicated across protocol/host variants (no redirect)

Rule duplicate.protocol_host · Duplicate · 3 occurrence(s)

  • https://olioa.co.jp/ — http://olioa.co.jp/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.
  • https://olioa.co.jp/ — http://www.olioa.co.jp/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.
  • https://olioa.co.jp/ — https://www.olioa.co.jp/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 2 occurrence(s)

warning Content-Type header doesn't match the actual content

Rule headers.content_type_mismatch · Security · 18 occurrence(s)

  • https://olioa.co.jp/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-branding.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-dtp.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-photo.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-web-consulting.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-web-contact.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-web-detail.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-web-failure.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-web-flow.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-web-price.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-web-production.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-web-subsidy.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/business-web.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/company.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/contact.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/index.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/privacy.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://olioa.co.jp/team.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".

warning Page is noindex

Rule index.noindex · Indexability · 1 occurrence(s)

Notices (13 rules)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

  • https://olioa.co.jp/ — no llms.txt found at the site root — add one so AI agents get a curated site summary

notice No main landmark for AI agents

Rule agent.no_main_landmark · Agent Readiness · 16 occurrence(s)

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 2 occurrence(s)

notice Likely hero image lacks fetchpriority=high

Rule images.hero_no_fetchpriority · Performance · 18 occurrence(s)

  • https://olioa.co.jp/ — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-branding.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-dtp.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-photo.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-web-consulting.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-web-contact.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-web-detail.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-web-failure.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-web-flow.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-web-price.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-web-production.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-web-subsidy.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/business-web.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/company.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/contact.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/index.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/privacy.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://olioa.co.jp/team.html — the likely hero/LCP image (logo-symbol.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.

notice Images without width/height (layout shift / CLS)

Rule images.missing_dimensions · Images · 18 occurrence(s)

notice Page has only one internal inlink (fragile crawl path)

Rule links.single_inlink · Links · 1 occurrence(s)

notice Meta description too short

Rule meta_desc.too_short · Meta Description · 2 occurrence(s)

notice Missing Open Graph tags

Rule og.missing · Social · 17 occurrence(s)

notice No structured data detected

Rule schema.none · Structured Data · 17 occurrence(s)

notice Missing recommended security headers

Rule security.missing_headers · Security · 18 occurrence(s)

notice Indexable page not listed in sitemap

Rule sitemap.orphan_not_listed · Sitemap · 1 occurrence(s)

notice Title is very short

Rule title.too_short · Titles · 9 occurrence(s)

notice Missing Twitter Card tag

Rule twitter.missing · Social · 17 occurrence(s)

Pages (showing 18 of 18)
URLStatusIndexableWordsIn-links
https://olioa.co.jp/index.html
OLIOA｜Brand new tomorrow		 200 yes 162 18
https://olioa.co.jp/privacy.html
Privacy Policy｜OLIOA		 200 no 64 18
https://olioa.co.jp/company.html
Company｜OLIOA		 200 yes 125 10
https://olioa.co.jp/team.html
Team O.｜OLIOA		 200 yes 152 10
https://olioa.co.jp/contact.html
Contact｜OLIOA		 200 yes 55 10
https://olioa.co.jp/business-web.html
Web Design｜OLIOA		 200 yes 89 10
https://olioa.co.jp/business-web-consulting.html
Webコンサルティング｜OLIOA		 200 yes 83 9
https://olioa.co.jp/business-web-contact.html
Webの方向性整理・無料相談｜OLIOA		 200 yes 58 9
https://olioa.co.jp/business-web-flow.html
制作の流れ｜OLIOA		 200 yes 76 9
https://olioa.co.jp/business-web-price.html
価格の考え方｜OLIOA		 200 yes 237 9
https://olioa.co.jp/business-web-production.html
ホームページ制作｜OLIOA		 200 yes 91 9
https://olioa.co.jp/business-web-failure.html
よくある失敗例｜OLIOA		 200 yes 70 8
https://olioa.co.jp/business-branding.html
Corporate Branding｜OLIOA		 200 yes 82 2
https://olioa.co.jp/business-dtp.html
DTP Design｜OLIOA		 200 yes 78 2
https://olioa.co.jp/business-photo.html
Photography｜OLIOA		 200 yes 77 2
https://olioa.co.jp/business-web-subsidy.html
補助金サポート｜OLIOA		 200 yes 102 4
https://olioa.co.jp/business-web-detail.html
料金・プラン詳細｜OLIOA		 200 yes 89 1
https://olioa.co.jp/
OLIOA｜Brand new tomorrow		 200 yes 162 0

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →