SEO report for robotstart.info
https://robotstart.info/ · checked Sun, 01 Nov 2026 18:16 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.
- 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.
- 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
“ロボスタ - ロボット･AI情報WEBマガジン”
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.
- Heading structuremedium
93 headings for 432 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- 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.
- 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.
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 robotstart.info…
Indexing & crawling 88%
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.
- ✓
Canonical URLhigh
Canonical: https://robotstart.info/
Points to this page (self-referencing).
- ✓
Redirectshigh
Loads directly with no redirects.
- ✓
www / non-wwwmedium
www.robotstart.info isn't in use (HTTP 530).
Search snippet & sharing 79%
How the page looks in Google results and when shared.
- !
Title tagcritical
“ロボスタ - ロボット･AI情報WEBマガジン”
About 249px 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
66 characters, ~509px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="ja"
Content quality 54%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
432 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.
- i
Readabilitymedium
Reading-ease scores only work for English; this page is lang="ja".
- !
Topic focushigh
2 of 3 title keywords appear in the main content (missing: ai情報webマガジン).
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
93 headings for 432 words – a lot for the amount of text.
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
12% of the HTML is visible text.
AI search readiness 50%
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
The page shows when it was published or last updated.
- ✗
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 70%
Machine-readable facts for rich results and AI.
- !
JSON-LD present & validhigh
2 JSON-LD block(s): BreadcrumbList, ListItem.
Block 2: invalid JSON
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 56%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
141 internal and 130 external links.
- ✗
Anchor text qualitymedium
Same text used for 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”.
- !
Broken links (sample)high
Checked 12 internal link(s).
Broken: /pages/info/members.html (404).
3 link(s) point to a redirect – link to the final address instead.
Fix: Fix or remove links that return errors, and update links that redirect.
Performance 50%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- !
Server response (TTFB)high
1378 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
123 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
14 script tag(s); files loaded from 5 other domain(s): securepubads.g.doubleclick.net, facebook.com, googletagmanager.com, front-api-gateway.account.media.iid.jp, cdn.rocket-push.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- !
Imagesmedium
108 image(s).
All images reserve their space.
105 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.
- ✗
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 58%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=2.0, user-scalable=yes
- ✓
Image alt textmedium
All 108 images have alt text.
- ✗
Form labelsmedium
1 of 3 form field(s) have no label.
Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).
- ✗
Link nameslow
3 link(s) have no readable name for screen readers.
Fix: Add text or aria-label to icon-only links.
- ✗
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.