Catalog / sd-energy.jp
77

SEO audit for sd-energy.jp

SDE-エスディーエナジー株式会社

other

Health 77/100 (good) · 31 pages crawled · generated 2026-08-26

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

エスディーエナジー株式会社は、増え続ける災害時にも企業継続のお役に立てる非常用電源装置「E.P.S mobile シリーズ」を中心とした製品の研究開発・販売を行っています。

Screenshot of sd-energy.jp
31
pages crawled
18
indexable pages
0
errors
67
warnings
219
notices
0
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Canonical 83 0 18 0
Content 83 0 18 18
Security 83 0 18 18
Duplicate 89 0 11 8
Images 98 0 2 20
Agent Readiness 100 0 0 19
Meta Description 100 0 0 15
Performance 100 0 0 43
Robots 100 0 0 1
Sitemap 100 0 0 4
Social 100 0 0 36
Structured Data 100 0 0 18
URL 100 0 0 19
Findings

Warnings (6 rules)

warning Missing canonical tag

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

warning Thin content (low word count)

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

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

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

  • https://sd-energy.jp/ — http://sd-energy.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://sd-energy.jp/ — http://www.sd-energy.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://sd-energy.jp/ — https://www.sd-energy.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 · 8 occurrence(s)

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

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

  • https://sd-energy.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://sd-energy.jp/business.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://sd-energy.jp/case-jiseikai-hospital.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://sd-energy.jp/case-sanyo-bm.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://sd-energy.jp/cases.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://sd-energy.jp/cases_tekken.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://sd-energy.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://sd-energy.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://sd-energy.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://sd-energy.jp/products-alive.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://sd-energy.jp/products-cube.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://sd-energy.jp/products-festar.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://sd-energy.jp/products-miniplus.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://sd-energy.jp/products-mobile.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://sd-energy.jp/products-option.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://sd-energy.jp/products-others.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://sd-energy.jp/products-tough.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://sd-energy.jp/recruit.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 Images missing alt text

Rule images.missing_alt · Images · 2 occurrence(s)

Notices (19 rules)

notice No llms.txt for AI agents

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

  • https://sd-energy.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 · 18 occurrence(s)

notice Duplicate meta description across pages

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

notice Image filename is generic/auto-generated (missed image-search signal)

Rule images.generic_filename · Images · 2 occurrence(s)

  • https://sd-energy.jp/ — 6 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
  • https://sd-energy.jp/index.html — 6 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.

notice Likely hero image lacks fetchpriority=high

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

  • https://sd-energy.jp/ — the likely hero/LCP image (logo.png) 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://sd-energy.jp/business.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/case-jiseikai-hospital.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/case-sanyo-bm.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/cases.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/cases_tekken.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/company.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/contact.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/index.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/products-alive.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/products-cube.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/products-festar.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/products-miniplus.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/products-mobile.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/products-option.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/products-others.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/products-tough.html — the likely hero/LCP image (logo.png) 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://sd-energy.jp/recruit.html — the likely hero/LCP image (logo.png) 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 Legacy <meta name=keywords> tag present (Google ignores it)

Rule meta.keywords_present · Content · 18 occurrence(s)

notice Meta description too short

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

notice Missing Open Graph tags

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

notice Legacy image format (jpg/png/gif) with no next-gen fallback

Rule perf.images_legacy_format · Performance · 18 occurrence(s)

  • https://sd-energy.jp/ — 12 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/business.html — 6 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/case-jiseikai-hospital.html — 6 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/case-sanyo-bm.html — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/cases.html — 6 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/cases_tekken.html — 6 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/company.html — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/contact.html — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/index.html — 12 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/products-alive.html — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/products-cube.html — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/products-festar.html — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/products-miniplus.html — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/products-mobile.html — 7 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/products-option.html — 7 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/products-others.html — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/products-tough.html — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://sd-energy.jp/recruit.html — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.

notice Large HTML document

Rule perf.large_html · Performance · 3 occurrence(s)

notice Slow server response

Rule perf.slow_response · Performance · 4 occurrence(s)

notice robots.txt missing (root returns 404/none)

Rule robots.txt_missing · Robots · 1 occurrence(s)

  • https://sd-energy.jp/ — robots.txt did not return a 200 at the site root — a healthy site should serve one (declare your sitemap and confirm the host serves root files)

notice No structured data detected

Rule schema.none · Structured Data · 18 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 · 4 occurrence(s)

notice Missing Twitter Card tag

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

notice Underscores in URL path (prefer hyphens)

Rule url.underscores · URL · 10 occurrence(s)

notice Uppercase letters in URL path

Rule url.uppercase · URL · 9 occurrence(s)

Pages (showing 31 of 31)
URLStatusIndexableWordsIn-links
https://sd-energy.jp/cases.html
導入事例 | エスディーエナジー株式会社		 200 yes 149 18
https://sd-energy.jp/contact.html
お問合わせ　| エスディーエナジー株式会社		 200 yes 64 18
https://sd-energy.jp/index.html
SDE-エスディーエナジー株式会社		 200 yes 173 18
https://sd-energy.jp/products-alive.html
製品紹介　E.P.S mobile ALIVE| エスディーエナジー株式会社		 200 yes 80 18
https://sd-energy.jp/products-cube.html
製品紹介　E.P.S mobile CUBE | エスディーエナジー株式会社		 200 yes 79 18
https://sd-energy.jp/products-festar.html
製品紹介　E.P.S FESTAR | エスディーエナジー株式会社		 200 yes 81 18
https://sd-energy.jp/products-miniplus.html
製品紹介　E.P.S mobile MINIPLUS | エスディーエナジー株式会社		 200 yes 79 18
https://sd-energy.jp/products-option.html
製品紹介　E.P.S mobile オプション | エスディーエナジー株式会社		 200 yes 93 18
https://sd-energy.jp/products-others.html
製品紹介　E.P.S mobile オプション | エスディーエナジー株式会社		 200 yes 75 18
https://sd-energy.jp/products-tough.html
製品紹介　E.P.S TOUGH | エスディーエナジー株式会社		 200 yes 81 18
https://sd-energy.jp/recruit.html
採用情報 | エスディーエナジー株式会社		 200 yes 70 18
https://sd-energy.jp/business.html
事業内容 | エスディーエナジー株式会社		 200 yes 94 17
https://sd-energy.jp/company.html
会社案内 | エスディーエナジー株式会社		 200 yes 152 17
https://sd-energy.jp/case-jiseikai-hospital.html
導入事例 | エスディーエナジー株式会社		 200 yes 92 3
https://sd-energy.jp/case-sanyo-bm.html
導入事例 | エスディーエナジー株式会社		 200 yes 88 3
https://sd-energy.jp/cases_tekken.html
導入事例 | エスディーエナジー株式会社		 200 yes 100 3
https://sd-energy.jp/products-mobile.html
製品情報　E.P.S mobile シリーズ | エスディーエナジー株式会社		 200 yes 151 2
https://sd-energy.jp/
SDE-エスディーエナジー株式会社		 200 yes 173 0
https://sd-energy.jp/pdf/20250831_exhibitionPDF.pdf 200 no 0 2
https://sd-energy.jp/pdf/20250901_RISCON_TOKYO_PDF.pdf 200 no 0 2
https://sd-energy.jp/pdf/20251031_RISCON_PDF.pdf 200 no 0 2
https://sd-energy.jp/pdf/ALIVE.pdf 200 no 0 2
https://sd-energy.jp/pdf/CUBE.pdf 200 no 0 2
https://sd-energy.jp/pdf/FESTAR_01.pdf 200 no 0 1
https://sd-energy.jp/pdf/MINIPLUS.pdf 200 no 0 2
https://sd-energy.jp/pdf/POWER.pdf 200 no 0 0
https://sd-energy.jp/pdf/TOUGH_01.pdf 200 no 0 1
https://sd-energy.jp/pdf/event_%2020240805.pdf 200 no 0 2
https://sd-energy.jp/pdf/event_%2020250625.pdf 200 no 0 2
https://sd-energy.jp/pdf/event_20241118.pdf 200 no 0 2
https://sd-energy.jp/pdf/information_20250703.pdf 200 no 0 2

Audit your own site — free

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

Scan your site →