SEO report for impress.co.jp

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 impress.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

  robots.txt found.

  Googlebot is allowed to crawl this page.

• ✗

  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.

  Make one with the free XML sitemap generator

  Read the guide: XML sitemaps

• ✗

  Canonical URLhigh

  No canonical tag.

  Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.

  Read the guide: duplicate content

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✗

  www / non-wwwmedium

  Both www.impress.co.jp and impress.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 46%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “株式会社インプレス”

  About 100px 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.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• ✗

  Meta descriptionhigh

  No meta description – Google will pick text from the page.

  Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

  Write one free with the AI title & description writer

  Read the guide: how to write meta descriptions

• ✓

  Open Graph & social cardsmedium

  Open Graph title and image set.

  No twitter:card tag.

• ✗

  Faviconlow

  No favicon linked.

  Fix: Add a square favicon at least 48×48px.

• ✓

  Languagelow

  lang="ja"

Content quality 54%

Is there enough clear, useful text that matches what the page targets?

• ✗

  Word countmedium

  26 words of main content (menus and footer excluded).

  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.

  Count words and keywords with the free word counter

  Read the guide: how to write SEO content

• i

  Readabilitymedium

  Reading-ease scores only work for English; this page is lang="ja".

• ✓

  Topic focushigh

  1 of 1 title keywords appear in the main content.

• !

  H1 headingcritical

  “”

  The H1 is empty.

  Fix: Use one H1 that states the page topic with its main keyword.

• !

  Heading structuremedium

  10 headings for 26 words.

  1 skipped level(s), e.g. H2 → H4.

  2 empty heading(s).

  Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  Read the guide: the on-page SEO checklist

• !

  Text-to-code ratiolow

  5% of the HTML is visible text.

  Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 66%

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.

  Make one with the free llms.txt generator

  Read the guide: do you need llms.txt?

• ✗

  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.

  Read the guide: how to write SEO content

• !

  Entity clarityhigh

  Identified as: Corporation.

  No sameAs links to official profiles (Google Business Profile, LinkedIn, Facebook, Companies House…).

  Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Freshness signalsmedium

  The page shows when it was published or last updated.

• !

  Trust pages (E-E-A-T)medium

  Links found to contact and privacy; missing about.

  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 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  1 JSON-LD block(s): WebSite, Corporation.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  40 internal and 11 external links.

• ✗

  Anchor text qualitymedium

  No link text points to two different pages.

  3 link(s) with no text at all.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

  1 link(s) point to a redirect – link to the final address instead.

Performance 58%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

• !

  Server response (TTFB)high

  923 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

  22 kB of HTML.

• i

  Compressionmedium

  Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.

• ✓

  Render-blocking resourceshigh

  0 blocking script(s) and 2 stylesheet(s) in <head>.

• !

  Scripts & third partiesmedium

  13 script tag(s); files loaded from 3 other domain(s): googletagmanager.com, google.com, ajax.googleapis.com.

  Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  21 image(s).

  8 without width/height – can cause layout shift (CLS).

  18 image(s) after the first three aren't lazy-loaded.

  0 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.

  Read the guide: image SEO

• ✗

  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 92%

Visitor safety signals that browsers and Google check.

• ✓

  HTTPScritical

  Secure HTTPS with no mixed content.

• ✓

  HTTP → HTTPS redirecthigh

  http:// redirects to https:// (via 2 hops).

• ✓

  HSTSmedium

  HSTS: max-age=31536000

• ✗

  Security headerslow

  Present: none.

  Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  Read the guide: the technical SEO checklist

• ✓

  Server fingerprintlow

  No X-Powered-By header (server: cloudflare).

Mobile & accessibility 35%

Usable on phones and by everyone – Google indexes the mobile version.

• !

  Mobile viewportcritical

  viewport: width=device-width, initial-scale=1.0, user-scalable=no, minimum-scale=1.0, maximum-scale=1.0 – blocks pinch-zoom

  Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.

  Read the guide: mobile-friendly websites

• !

  Image alt textmedium

  1 of 21 images have no alt attribute.

  Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).

  Read the guide: image SEO

• ✗

  Link nameslow

  3 link(s) have no readable name for screen readers.

  Fix: Add text or aria-label to icon-only links.

  Read the guide: internal linking

• ✗

  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.

  Read the guide: mobile-friendly websites

Local SEO 17%

Signals that help you appear in Google Maps and 'near me' searches.

• ✗

  LocalBusiness markuphigh

  No LocalBusiness structured data.

  Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✗

  Contact details on pagemedium

  No phone number found.

  No postcode found (fine for service-area businesses).

  Fix: Show the same business name, area and phone/email as your Google Business Profile.

  Read the guide: the local SEO checklist

• ✓

  Map & directionslow

  Links to or embeds a map.