SEO report for procommit.co.jp
https://procommit.co.jp/ · checked Wed, 11 Nov 2026 08:17 GMT
Fix these first
- XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- Topic focushigh
0 of 1 title keywords appear in the main content (missing: 株式会社プロコミット).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
- Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- Server response (TTFB)high
1857 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.
- Render-blocking resourceshigh
2 blocking script(s) and 1 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- Title tagcritical
“株式会社プロコミット”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- H1 headingcritical
“”
Fix: Use one H1 that states the page topic with its main keyword.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to procommit.co.jp…
Indexing & crawling 67%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- !
robots.txthigh
No robots.txt found (HTTP 404) – crawlers may read everything.
Googlebot is allowed to crawl this page.
Fix: Add a robots.txt that allows crawling and lists your sitemap.
- ✗
XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- !
Canonical URLhigh
Canonical: https://www.procommit.co.jp/
Points to a DIFFERENT address – Google will probably index that one instead of this page.
The canonical uses the other www / non-www version of your domain.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- ✓
Redirectshigh
Loads directly with no redirects.
- ✗
www / non-wwwmedium
Both www.procommit.co.jp and procommit.co.jp load without redirecting – Google may see duplicate sites.
Fix: Pick one version (with or without www) and 301-redirect the other to it.
Search snippet & sharing 67%
How the page looks in Google results and when shared.
- !
Title tagcritical
“株式会社プロコミット”
About 111px of Google's ~580px desktop width – short; use the space.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- !
Meta descriptionhigh
63 characters, ~491px of ~990px.
Short – sell the click with a benefit and a call to action.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="ja"
Content quality 27%
Is there enough clear, useful text that matches what the page targets?
- ✗
Word countmedium
7 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.
- i
Readabilitymedium
Reading-ease scores only work for English; this page is lang="ja".
- ✗
Topic focushigh
0 of 1 title keywords appear in the main content (missing: 株式会社プロコミット).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
- !
H1 headingcritical
“”
The H1 is empty.
Fix: Use one H1 that states the page topic with its main keyword.
- !
Heading structuremedium
3 headings for 7 words.
Levels are in order.
1 empty heading(s).
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
3% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 38%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✗
Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- ✗
Trust pages (E-E-A-T)medium
No links found to about, contact or privacy pages.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 0%
Machine-readable facts for rich results and AI.
- ✗
JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
Links 81%
Internal linking, anchor text and broken links.
- !
Internal linkinghigh
2 internal and 2 external links.
Fix: Link to your most important pages from this page with descriptive text.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 1 internal link(s).
No broken links found.
Performance 40%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✗
Server response (TTFB)high
1857 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.
- ✓
HTML sizemedium
5 kB of HTML.
- ✓
Compressionmedium
Compressed with gzip.
- ✗
Render-blocking resourceshigh
2 blocking script(s) and 1 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✓
Scripts & third partiesmedium
3 script tag(s); files loaded from 2 other domain(s): code.jquery.com, cdnjs.cloudflare.com.
- ✗
Imagesmedium
3 image(s).
3 without width/height – can cause layout shift (CLS).
2 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✗
Cachinglow
No Cache-Control header.
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 75%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✗
HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- ✗
Security headerslow
Present: nosniff.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 80%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✓
Image alt textmedium
All 3 images have alt text.
- ✓
Link nameslow
Every link has a readable name.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
- i
Map & directionslow
No map or directions link.