SEO audit for maedashoten.com
Salesforce導入支援|秋田発・全国対応の中小企業向けコンサルティング|前田商店
Health 65/100 (fair) · 12 pages crawled · generated 2026-08-26
Download Markdown report (feed to ChatGPT / Claude / Cursor)Salesforce導入支援を中心に、Tableau・Yoom・Google Workspaceまで対応。中小企業が「使いこなせる」設計を、営業視点×PM経験で実現します。まず30分の無料相談から。前田商店。
| Category | Score | Errors | Warnings | Notices |
|---|---|---|---|---|
| Links | 70 | 0 | 12 | 4 |
| Security | 70 | 0 | 12 | 12 |
| Content | 80 | 0 | 8 | 13 |
| Duplicate | 90 | 0 | 4 | 2 |
| Agent Readiness | 100 | 0 | 0 | 13 |
| Crawlability | 100 | 0 | 0 | 1 |
| Meta Description | 100 | 0 | 0 | 2 |
| Performance | 100 | 0 | 0 | 12 |
| Social | 100 | 0 | 0 | 4 |
| Structured Data | 100 | 0 | 0 | 8 |
| Titles | 100 | 0 | 0 | 1 |
Warnings (5 rules)
warning Thin content (low word count)
Rule content.thin · Content · 8 occurrence(s)
- https://www.maedashoten.com/case-studies.html — 83 words
- https://www.maedashoten.com/cases/case-01-salesforce-subscription-service.html — 108 words
- https://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.html — 108 words
- https://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.html — 113 words
- https://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.html — 115 words
- https://www.maedashoten.com/dev-environment.html — 150 words
- https://www.maedashoten.com/privacy-policy.html — 183 words
- https://www.maedashoten.com/terms.html — 145 words
warning Duplicate page content
Rule duplicate.content · Duplicate · 2 occurrence(s)
- https://www.maedashoten.com/ — content shared by 2 pages: https://www.maedashoten.com/index.html
- https://www.maedashoten.com/index.html — content shared by 2 pages: https://www.maedashoten.com/
warning Duplicate <title> across pages
Rule duplicate.title · Duplicate · 2 occurrence(s)
- https://www.maedashoten.com/ — title shared by 2 pages: https://www.maedashoten.com/index.html
- https://www.maedashoten.com/index.html — title shared by 2 pages: https://www.maedashoten.com/
warning Content-Type header doesn't match the actual content
Rule headers.content_type_mismatch · Security · 12 occurrence(s)
- https://www.maedashoten.com/ — 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://www.maedashoten.com/case-studies.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://www.maedashoten.com/cases/case-01-salesforce-subscription-service.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://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.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://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.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://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.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://www.maedashoten.com/dev-environment.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://www.maedashoten.com/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://www.maedashoten.com/pricing.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://www.maedashoten.com/privacy-policy.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://www.maedashoten.com/profile.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://www.maedashoten.com/terms.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 Internal link points to a redirect
Rule links.redirect_target · Links · 12 occurrence(s)
- https://www.maedashoten.com/ — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/case-studies.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/cases/case-01-salesforce-subscription-service.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/dev-environment.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/index.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/pricing.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/privacy-policy.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/profile.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
- https://www.maedashoten.com/terms.html — https://www.maedashoten.com/index.html → https://www.maedashoten.com/
Notices (16 rules)
notice No llms.txt for AI agents
Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)
- https://www.maedashoten.com/ — 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 · 12 occurrence(s)
- https://www.maedashoten.com/ — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/case-studies.html — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/cases/case-01-salesforce-subscription-service.html — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.html — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.html — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.html — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/dev-environment.html — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/index.html — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/pricing.html — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/privacy-policy.html — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/profile.html — add a <main> element (or role=main) around the primary content
- https://www.maedashoten.com/terms.html — add a <main> element (or role=main) around the primary content
notice Duplicate meta description across pages
Rule duplicate.meta_desc · Duplicate · 2 occurrence(s)
- https://www.maedashoten.com/ — meta description shared by 2 pages: https://www.maedashoten.com/index.html
- https://www.maedashoten.com/index.html — meta description shared by 2 pages: https://www.maedashoten.com/
notice Article page has no publication date (freshness / E-E-A-T)
Rule eeat.no_date · Content · 4 occurrence(s)
- https://www.maedashoten.com/cases/case-01-salesforce-subscription-service.html — this page is marked up as an article but has no publication date — no datePublished in its JSON-LD and no visible date — add a visible published date and an Article.datePublished so Google can assess freshness
- https://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.html — this page is marked up as an article but has no publication date — no datePublished in its JSON-LD and no visible date — add a visible published date and an Article.datePublished so Google can assess freshness
- https://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.html — this page is marked up as an article but has no publication date — no datePublished in its JSON-LD and no visible date — add a visible published date and an Article.datePublished so Google can assess freshness
- https://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.html — this page is marked up as an article but has no publication date — no datePublished in its JSON-LD and no visible date — add a visible published date and an Article.datePublished so Google can assess freshness
notice Likely hero image lacks fetchpriority=high
Rule images.hero_no_fetchpriority · Performance · 12 occurrence(s)
- https://www.maedashoten.com/ — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/case-studies.html — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/cases/case-01-salesforce-subscription-service.html — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.html — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.html — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.html — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/dev-environment.html — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/index.html — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/pricing.html — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/privacy-policy.html — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/profile.html — the likely hero/LCP image (logo_emblem.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://www.maedashoten.com/terms.html — the likely hero/LCP image (logo_emblem.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 Page has only one internal inlink (fragile crawl path)
Rule links.single_inlink · Links · 4 occurrence(s)
- https://www.maedashoten.com/cases/case-01-salesforce-subscription-service.html — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
- https://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.html — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
- https://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.html — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
- https://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.html — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.
notice Legacy <meta name=keywords> tag present (Google ignores it)
Rule meta.keywords_present · Content · 9 occurrence(s)
- https://www.maedashoten.com/ — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://www.maedashoten.com/case-studies.html — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://www.maedashoten.com/cases/case-01-salesforce-subscription-service.html — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.html — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.html — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.html — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://www.maedashoten.com/dev-environment.html — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://www.maedashoten.com/index.html — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://www.maedashoten.com/pricing.html — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
notice Meta description too short
Rule meta_desc.too_short · Meta Description · 2 occurrence(s)
- https://www.maedashoten.com/privacy-policy.html — 38 chars
- https://www.maedashoten.com/terms.html — 33 chars
notice Missing Open Graph tags
Rule og.missing · Social · 2 occurrence(s)
- https://www.maedashoten.com/privacy-policy.html — og:title, og:description, og:image
- https://www.maedashoten.com/terms.html — og:title, og:description, og:image
notice URL redirects to another URL
Rule redirect.single · Crawlability · 1 occurrence(s)
- https://www.maedashoten.com/index.html — redirects to https://www.maedashoten.com/
notice Article schema missing recommended properties (Top Stories / image carousel)
Rule schema.article_incomplete · Structured Data · 4 occurrence(s)
- https://www.maedashoten.com/cases/case-01-salesforce-subscription-service.html — Article structured data is missing recommended properties (image, datePublished) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- https://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.html — Article structured data is missing recommended properties (image, datePublished) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- https://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.html — Article structured data is missing recommended properties (image, datePublished) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- https://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.html — Article structured data is missing recommended properties (image, datePublished) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
notice FAQPage structured data (rich result removed May 2026)
Rule schema.faq_deprecated · Structured Data · 2 occurrence(s)
- https://www.maedashoten.com/ — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
- https://www.maedashoten.com/index.html — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
notice No structured data detected
Rule schema.none · Structured Data · 2 occurrence(s)
notice Missing recommended security headers
Rule security.missing_headers · Security · 12 occurrence(s)
- https://www.maedashoten.com/ — HSTS, CSP, X-Content-Type-Options
- https://www.maedashoten.com/case-studies.html — HSTS, CSP, X-Content-Type-Options
- https://www.maedashoten.com/cases/case-01-salesforce-subscription-service.html — X-Content-Type-Options, HSTS, CSP
- https://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.html — HSTS, CSP, X-Content-Type-Options
- https://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.html — HSTS, CSP, X-Content-Type-Options
- https://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.html — HSTS, CSP, X-Content-Type-Options
- https://www.maedashoten.com/dev-environment.html — X-Content-Type-Options, HSTS, CSP
- https://www.maedashoten.com/index.html — HSTS, CSP, X-Content-Type-Options
- https://www.maedashoten.com/pricing.html — CSP, X-Content-Type-Options, HSTS
- https://www.maedashoten.com/privacy-policy.html — X-Content-Type-Options, HSTS, CSP
- https://www.maedashoten.com/profile.html — CSP, X-Content-Type-Options, HSTS
- https://www.maedashoten.com/terms.html — CSP, X-Content-Type-Options, HSTS
notice Title is very short
Rule title.too_short · Titles · 1 occurrence(s)
- https://www.maedashoten.com/terms.html — 9 chars
notice Missing Twitter Card tag
Rule twitter.missing · Social · 2 occurrence(s)
| URL | Status | Indexable | Words | In-links |
|---|---|---|---|---|
| https://www.maedashoten.com/case-studies.html 事例紹介|Salesforce・Tableau・Yoom・Google Workspace導入支援の実績|前田商店 |
200 | yes | 83 | 12 |
| https://www.maedashoten.com/dev-environment.html Salesforce導入支援の開発環境|VS Code・Git・AI活用で品質とスピードを両立|前田商店 |
200 | yes | 150 | 12 |
| https://www.maedashoten.com/index.html Salesforce導入支援|秋田発・全国対応の中小企業向けコンサルティング|前田商店 |
200 | yes | 313 | 12 |
| https://www.maedashoten.com/pricing.html 価格・ご支援内容|前田商店|Salesforce・Tableau・Yoom・Google Workspace 導入支援 |
200 | yes | 216 | 12 |
| https://www.maedashoten.com/privacy-policy.html プライバシーポリシー|前田商店 |
200 | yes | 183 | 12 |
| https://www.maedashoten.com/profile.html 代表プロフィール|前田 学|前田商店 |
200 | yes | 433 | 12 |
| https://www.maedashoten.com/terms.html 利用規約|前田商店 |
200 | yes | 145 | 12 |
| https://www.maedashoten.com/cases/case-01-salesforce-subscription-service.html 【事例】Googleスプレッドシート管理からSalesforceへ|サービス業・小規模|前田商店 |
200 | yes | 108 | 1 |
| https://www.maedashoten.com/cases/case-02-salesforce-zoomphone-integration.html 【事例】Zoom PhoneとSalesforce連携で電話対応を一元管理|サービス業・40名規模|前田商店 |
200 | yes | 108 | 1 |
| https://www.maedashoten.com/cases/case-03-salesforce-multi-department-recordtypes.html 【事例】5つの事業部の顧客情報をSalesforceで一元管理|サービス業・40名規模|前田商店 |
200 | yes | 113 | 1 |
| https://www.maedashoten.com/cases/case-04-salesforce-tableau-partner-scoring.html 【事例】属人的だった取引先評価を自動スコアリング化し、"先読み"で離脱を防ぐ仕組みへ|不動産業・30名規模|前田商店 |
200 | yes | 115 | 1 |
| https://www.maedashoten.com/ Salesforce導入支援|秋田発・全国対応の中小企業向けコンサルティング|前田商店 |
200 | yes | 313 | 0 |
Audit your own site — free
157 checks, internal PageRank, render-diff. No signup, results in ~30s.