SEO audit for centre.us
Centre Innovation Group | Technology Consulting & Managed Services
Health 65/100 (fair) · 10 pages crawled · generated 2026-08-26
Download Markdown report (feed to ChatGPT / Claude / Cursor)Centre Innovation Group delivers technology consulting and managed services — 24/7 operations, IT infrastructure, managed security, and solution delivery for enterprise growth.
| Category | Score | Errors | Warnings | Notices |
|---|---|---|---|---|
| Links | 0 | 0 | 50 | 1 |
| Security | 70 | 0 | 10 | 10 |
| Agent Readiness | 100 | 0 | 0 | 2 |
| Cache | 100 | 0 | 0 | 1 |
| Content | 100 | 0 | 0 | 18 |
| Crawlability | 100 | 0 | 0 | 9 |
| Headings | 100 | 0 | 0 | 7 |
| Images | 100 | 0 | 0 | 10 |
| Meta Description | 100 | 0 | 0 | 3 |
| Performance | 100 | 0 | 0 | 21 |
| Social | 100 | 0 | 0 | 10 |
| Structured Data | 100 | 0 | 0 | 1 |
Warnings (2 rules)
warning Content-Type header doesn't match the actual content
Rule headers.content_type_mismatch · Security · 10 occurrence(s)
- https://centre.us/ — 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://centre.us/faq — 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://centre.us/privacy-policy — 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://centre.us/terms-of-use — 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://centre.us/use-cases — 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://centre.us/use-cases/catalyst-to-meraki-migration — 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://centre.us/use-cases/employee-lifecycle-automation — 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://centre.us/use-cases/it-helpdesk-transformation — 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://centre.us/use-cases/it-knowledge-intelligence — 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://centre.us/use-cases/security-remediation-compliance — 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 · 50 occurrence(s)
- https://centre.us/ — https://centre.us/faq → https://centre.us/faq/
- https://centre.us/ — https://centre.us/privacy-policy → https://centre.us/privacy-policy/
- https://centre.us/ — https://centre.us/terms-of-use → https://centre.us/terms-of-use/
- https://centre.us/ — https://centre.us/use-cases → https://centre.us/use-cases/
- https://centre.us/faq — https://centre.us/privacy-policy → https://centre.us/privacy-policy/
- https://centre.us/faq — https://centre.us/terms-of-use → https://centre.us/terms-of-use/
- https://centre.us/terms-of-use — https://centre.us/privacy-policy → https://centre.us/privacy-policy/
- https://centre.us/use-cases — https://centre.us/faq → https://centre.us/faq/
- https://centre.us/use-cases — https://centre.us/privacy-policy → https://centre.us/privacy-policy/
- https://centre.us/use-cases — https://centre.us/terms-of-use → https://centre.us/terms-of-use/
- https://centre.us/use-cases — https://centre.us/use-cases → https://centre.us/use-cases/
- https://centre.us/use-cases — https://centre.us/use-cases/catalyst-to-meraki-migration → https://centre.us/use-cases/catalyst-to-meraki-migration/
- https://centre.us/use-cases — https://centre.us/use-cases/employee-lifecycle-automation → https://centre.us/use-cases/employee-lifecycle-automation/
- https://centre.us/use-cases — https://centre.us/use-cases/it-helpdesk-transformation → https://centre.us/use-cases/it-helpdesk-transformation/
- https://centre.us/use-cases — https://centre.us/use-cases/it-knowledge-intelligence → https://centre.us/use-cases/it-knowledge-intelligence/
- https://centre.us/use-cases — https://centre.us/use-cases/security-remediation-compliance → https://centre.us/use-cases/security-remediation-compliance/
- https://centre.us/use-cases/catalyst-to-meraki-migration — https://centre.us/faq → https://centre.us/faq/
- https://centre.us/use-cases/catalyst-to-meraki-migration — https://centre.us/privacy-policy → https://centre.us/privacy-policy/
- https://centre.us/use-cases/catalyst-to-meraki-migration — https://centre.us/terms-of-use → https://centre.us/terms-of-use/
- https://centre.us/use-cases/catalyst-to-meraki-migration — https://centre.us/use-cases → https://centre.us/use-cases/
- https://centre.us/use-cases/catalyst-to-meraki-migration — https://centre.us/use-cases/employee-lifecycle-automation → https://centre.us/use-cases/employee-lifecycle-automation/
- https://centre.us/use-cases/catalyst-to-meraki-migration — https://centre.us/use-cases/it-helpdesk-transformation → https://centre.us/use-cases/it-helpdesk-transformation/
- https://centre.us/use-cases/catalyst-to-meraki-migration — https://centre.us/use-cases/security-remediation-compliance → https://centre.us/use-cases/security-remediation-compliance/
- https://centre.us/use-cases/it-helpdesk-transformation — https://centre.us/faq → https://centre.us/faq/
- https://centre.us/use-cases/it-helpdesk-transformation — https://centre.us/use-cases → https://centre.us/use-cases/
Notices (15 rules)
notice Heading levels skip a level
Rule agent.heading_skip · Agent Readiness · 2 occurrence(s)
- https://centre.us/ — h4 follows h2 — skips h3
- https://centre.us/use-cases — h3 follows h1 — skips h2
notice Page served uncached (no-store/private or CDN bypass)
Rule cache.not_cacheable · Cache · 1 occurrence(s)
- https://centre.us/ — Cache-Control: no-store, no-cache, must-revalidate
notice Main text is hard to read (low Flesch Reading Ease)
Rule content.readability_poor · Content · 8 occurrence(s)
- https://centre.us/ — this page reads as very difficult (Flesch Reading Ease -20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://centre.us/faq — this page reads as very difficult (Flesch Reading Ease 12, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://centre.us/use-cases — this page reads as very difficult (Flesch Reading Ease -3, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://centre.us/use-cases/catalyst-to-meraki-migration — this page reads as very difficult (Flesch Reading Ease -7, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://centre.us/use-cases/employee-lifecycle-automation — this page reads as very difficult (Flesch Reading Ease 1, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://centre.us/use-cases/it-helpdesk-transformation — this page reads as very difficult (Flesch Reading Ease 1, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://centre.us/use-cases/it-knowledge-intelligence — this page reads as very difficult (Flesch Reading Ease 1, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://centre.us/use-cases/security-remediation-compliance — this page reads as very difficult (Flesch Reading Ease -17, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
notice Multiple <h1> elements
Rule h1.multiple · Headings · 7 occurrence(s)
- https://centre.us/ — 2 <h1> elements
- https://centre.us/use-cases — 2 <h1> elements
- https://centre.us/use-cases/catalyst-to-meraki-migration — 2 <h1> elements
- https://centre.us/use-cases/employee-lifecycle-automation — 2 <h1> elements
- https://centre.us/use-cases/it-helpdesk-transformation — 2 <h1> elements
- https://centre.us/use-cases/it-knowledge-intelligence — 2 <h1> elements
- https://centre.us/use-cases/security-remediation-compliance — 2 <h1> elements
notice Likely hero image lacks fetchpriority=high
Rule images.hero_no_fetchpriority · Performance · 10 occurrence(s)
- https://centre.us/ — the likely hero/LCP image (b178fa36-a0cc-4a3d-baa1-76ce559cfd45_centre-logo-no-background.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://centre.us/faq — the likely hero/LCP image (b178fa36-a0cc-4a3d-baa1-76ce559cfd45_centre-logo-no-background.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://centre.us/privacy-policy — the likely hero/LCP image (b178fa36-a0cc-4a3d-baa1-76ce559cfd45_centre-logo-no-background.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://centre.us/terms-of-use — the likely hero/LCP image (b178fa36-a0cc-4a3d-baa1-76ce559cfd45_centre-logo-no-background.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://centre.us/use-cases — the likely hero/LCP image (b178fa36-a0cc-4a3d-baa1-76ce559cfd45_centre-logo-no-background.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://centre.us/use-cases/catalyst-to-meraki-migration — the likely hero/LCP image (b178fa36-a0cc-4a3d-baa1-76ce559cfd45_centre-logo-no-background.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://centre.us/use-cases/employee-lifecycle-automation — the likely hero/LCP image (b178fa36-a0cc-4a3d-baa1-76ce559cfd45_centre-logo-no-background.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://centre.us/use-cases/it-helpdesk-transformation — the likely hero/LCP image (b178fa36-a0cc-4a3d-baa1-76ce559cfd45_centre-logo-no-background.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://centre.us/use-cases/it-knowledge-intelligence — the likely hero/LCP image (b178fa36-a0cc-4a3d-baa1-76ce559cfd45_centre-logo-no-background.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://centre.us/use-cases/security-remediation-compliance — the likely hero/LCP image (b178fa36-a0cc-4a3d-baa1-76ce559cfd45_centre-logo-no-background.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 · 10 occurrence(s)
- https://centre.us/ — 30 of 30 images without width/height
- https://centre.us/faq — 1 of 1 images without width/height
- https://centre.us/privacy-policy — 1 of 1 images without width/height
- https://centre.us/terms-of-use — 1 of 1 images without width/height
- https://centre.us/use-cases — 3 of 3 images without width/height
- https://centre.us/use-cases/catalyst-to-meraki-migration — 3 of 3 images without width/height
- https://centre.us/use-cases/employee-lifecycle-automation — 3 of 3 images without width/height
- https://centre.us/use-cases/it-helpdesk-transformation — 3 of 3 images without width/height
- https://centre.us/use-cases/it-knowledge-intelligence — 3 of 3 images without width/height
- https://centre.us/use-cases/security-remediation-compliance — 3 of 3 images without width/height
notice Page has only one internal inlink (fragile crawl path)
Rule links.single_inlink · Links · 1 occurrence(s)
- https://centre.us/use-cases/catalyst-to-meraki-migration — 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 · 10 occurrence(s)
- https://centre.us/ — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://centre.us/faq — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://centre.us/privacy-policy — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://centre.us/terms-of-use — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://centre.us/use-cases — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://centre.us/use-cases/catalyst-to-meraki-migration — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://centre.us/use-cases/employee-lifecycle-automation — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://centre.us/use-cases/it-helpdesk-transformation — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://centre.us/use-cases/it-knowledge-intelligence — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://centre.us/use-cases/security-remediation-compliance — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
notice Meta description too long
Rule meta_desc.too_long · Meta Description · 3 occurrence(s)
- https://centre.us/ — 176 chars
- https://centre.us/use-cases/employee-lifecycle-automation — 167 chars
- https://centre.us/use-cases/security-remediation-compliance — 163 chars
notice Missing Open Graph tags
Rule og.missing · Social · 10 occurrence(s)
- https://centre.us/ — og:image
- https://centre.us/faq — og:image
- https://centre.us/privacy-policy — og:image
- https://centre.us/terms-of-use — og:image
- https://centre.us/use-cases — og:image
- https://centre.us/use-cases/catalyst-to-meraki-migration — og:image
- https://centre.us/use-cases/employee-lifecycle-automation — og:image
- https://centre.us/use-cases/it-helpdesk-transformation — og:image
- https://centre.us/use-cases/it-knowledge-intelligence — og:image
- https://centre.us/use-cases/security-remediation-compliance — og:image
notice Large DOM (over 1500 elements) slows rendering & interaction
Rule perf.dom_size_large · Performance · 1 occurrence(s)
- https://centre.us/ — the page has 1515 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
notice Legacy image format (jpg/png/gif) with no next-gen fallback
Rule perf.images_legacy_format · Performance · 10 occurrence(s)
- https://centre.us/ — 27 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://centre.us/faq — 1 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://centre.us/privacy-policy — 1 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://centre.us/terms-of-use — 1 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://centre.us/use-cases — 2 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://centre.us/use-cases/catalyst-to-meraki-migration — 2 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://centre.us/use-cases/employee-lifecycle-automation — 2 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://centre.us/use-cases/it-helpdesk-transformation — 2 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://centre.us/use-cases/it-knowledge-intelligence — 2 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://centre.us/use-cases/security-remediation-compliance — 2 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 URL redirects to another URL
Rule redirect.single · Crawlability · 9 occurrence(s)
- https://centre.us/faq — redirects to https://centre.us/faq/
- https://centre.us/privacy-policy — redirects to https://centre.us/privacy-policy/
- https://centre.us/terms-of-use — redirects to https://centre.us/terms-of-use/
- https://centre.us/use-cases — redirects to https://centre.us/use-cases/
- https://centre.us/use-cases/catalyst-to-meraki-migration — redirects to https://centre.us/use-cases/catalyst-to-meraki-migration/
- https://centre.us/use-cases/employee-lifecycle-automation — redirects to https://centre.us/use-cases/employee-lifecycle-automation/
- https://centre.us/use-cases/it-helpdesk-transformation — redirects to https://centre.us/use-cases/it-helpdesk-transformation/
- https://centre.us/use-cases/it-knowledge-intelligence — redirects to https://centre.us/use-cases/it-knowledge-intelligence/
- https://centre.us/use-cases/security-remediation-compliance — redirects to https://centre.us/use-cases/security-remediation-compliance/
notice FAQPage structured data (rich result removed May 2026)
Rule schema.faq_deprecated · Structured Data · 1 occurrence(s)
- https://centre.us/faq — 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 Missing recommended security headers
Rule security.missing_headers · Security · 10 occurrence(s)
- https://centre.us/ — HSTS, CSP, X-Content-Type-Options
- https://centre.us/faq — HSTS, CSP
- https://centre.us/privacy-policy — HSTS, CSP
- https://centre.us/terms-of-use — HSTS, CSP
- https://centre.us/use-cases — HSTS, CSP
- https://centre.us/use-cases/catalyst-to-meraki-migration — HSTS, CSP
- https://centre.us/use-cases/employee-lifecycle-automation — CSP, HSTS
- https://centre.us/use-cases/it-helpdesk-transformation — HSTS, CSP
- https://centre.us/use-cases/it-knowledge-intelligence — HSTS, CSP
- https://centre.us/use-cases/security-remediation-compliance — HSTS, CSP
| URL | Status | Indexable | Words | In-links |
|---|---|---|---|---|
| https://centre.us/ Centre Innovation Group | Technology Consulting & Managed Services |
200 | yes | 1740 | 9 |
| https://centre.us/privacy-policy Privacy Policy | Centre Innovation Group |
200 | yes | 1317 | 9 |
| https://centre.us/terms-of-use Terms of Use | Centre Innovation Group |
200 | yes | 1253 | 8 |
| https://centre.us/faq Frequently Asked Questions | Centre Innovation Group |
200 | yes | 3773 | 7 |
| https://centre.us/use-cases Use Cases & Client Stories | Centre Innovation Group |
200 | yes | 369 | 7 |
| https://centre.us/use-cases/it-helpdesk-transformation IT Helpdesk Transformation | Use Cases | Centre Innovation Group |
200 | yes | 807 | 5 |
| https://centre.us/use-cases/security-remediation-compliance Security Remediation & Compliance | Use Cases | Centre Innovation Group |
200 | yes | 762 | 5 |
| https://centre.us/use-cases/it-knowledge-intelligence IT Knowledge Intelligence | Use Cases | Centre Innovation Group |
200 | yes | 868 | 4 |
| https://centre.us/use-cases/employee-lifecycle-automation Employee Lifecycle Automation | Use Cases | Centre Innovation Group |
200 | yes | 801 | 4 |
| https://centre.us/use-cases/catalyst-to-meraki-migration Network Migration | Use Cases | Centre Innovation Group |
200 | yes | 760 | 1 |
Audit your own site — free
157 checks, internal PageRank, render-diff. No signup, results in ~30s.