Rapport SEO : inipec.gov.it
Généré le 1 mai 2026 · 28 constatations · 4.1s
Les sites institutionnels privilégient l'accessibilité, la sécurité et une indexation rigoureuse pour permettre aux citoyens et usagers d'accéder facilement à l'information.
Détail des scores
Score moyen Général : 50
Projection du score
Amélioration estimée sur la base des constatations identifiées dans ce rapport
Prêt à améliorer votre SEO ?
Commencez un essai gratuit et découvrez comment améliorer votre score.
Détail par module
Toutes les constatations (27)
Critique (15)
- highcookies
Could not fetch cookies
fetch failed
Ensure the website is accessible
- highcookies
Module failed
fetch failed
Try scanning again
- highssl
SSL certificate not found
Could not retrieve SSL certificate
Ensure the site has a valid SSL certificate installed
- highcookies
Module failed
fetch failed
Try scanning again
- highcookies
Module failed
fetch failed
Try scanning again
- highcookies
Module failed
fetch failed
Try scanning again
- highcookies
Module failed
fetch failed
Try scanning again
- highcookies
Module failed
fetch failed
Try scanning again
- highcookies
Module failed
fetch failed
Try scanning again
- highmobile
Missing viewport meta tag
No viewport meta tag found — page will not be mobile-responsive
Add <meta name="viewport" content="width=device-width, initial-scale=1">
- highcookies
Module failed
fetch failed
Try scanning again
- highcookies
Module failed
fetch failed
Try scanning again
- highcookies
Module failed
fetch failed
Try scanning again
- highcookies
Module failed
fetch failed
Try scanning again
- highcookies
Module failed
fetch failed
Try scanning again
Moyen (5)
- mediumdns
No DKIM record found
None of the common DKIM selectors returned a valid key. Email authentication may be incomplete.
Configure DKIM signing with your email provider and publish the public key in DNS
- mediumrate limits
No rate limiting detected
10 rapid requests all succeeded without any rate-limit headers or 429 responses. The site may be vulnerable to abuse.
Implement rate limiting (e.g., 429 Too Many Requests) to protect against brute-force attacks
- mediumlayout scan
No landmark elements
No semantic landmarks found (nav, main, header, footer)
Use semantic HTML5 landmarks for better accessibility and SEO
- mediumuptime checker
Intermittent failures
1 of 3 requests failed
Investigate server stability — intermittent failures hurt user experience and SEO
- mediumuptime checker
Inconsistent www handling
Both www and non-www versions respond with 200 — one should redirect to the other
Choose either www or non-www as canonical and redirect the other with a 301
Faible (7)
- lowdns
No IPv6 (AAAA) records
The domain has no AAAA records for IPv6 connectivity
Add AAAA DNS records for IPv6 support
- lowdns
DMARC policy is 'none'
DMARC is set but policy is 'none' (monitoring only).
Consider upgrading DMARC policy to 'quarantine' or 'reject'
- lowdns
DMARC reporting not configured
DMARC record does not have a rua= tag for aggregate reports.
Add rua=mailto:[email protected] to receive DMARC reports
- lowrate limits
No WAF detected
No Web Application Firewall (Cloudflare, AWS, Akamai, Vercel, Sucuri, Fastly) was detected in response headers.
Consider using a WAF to protect against common web attacks (XSS, SQL injection, DDoS)
- lowrate limits
No bot protection detected
No CAPTCHA, challenge page, or bot detection was triggered during rapid requests.
Consider implementing bot protection (e.g., Cloudflare Turnstile, hCaptcha) for sensitive endpoints
- lownews mentions
No press or news presence
No press pages found on the site and no external news mentions detected
Create a /news or /press page with company updates — this builds authority and earns links
- lowcrawl budget
No robots.txt found
No robots.txt file — no crawl directives
Add a robots.txt file with sitemap reference and crawl directives
AI Fix Prompt
Copiez ce prompt dans ChatGPT ou Claude pour obtenir des instructions de correction détaillées étape par étape
Fix all SEO issues found in the audit of inipec.gov.it.
Prioritize high-severity issues first, then medium. For each fix, make the actual code change — don't just describe what to do.
```json
{
"domain": "inipec.gov.it",
"scores": {
"overall": 61,
"performance": 0,
"seo": 85,
"accessibility": 50,
"bestPractices": 84,
"security": 36
},
"findings": [
{
"module": "cookies",
"severity": "high",
"title": "Could not fetch cookies",
"description": "fetch failed",
"recommendation": "Ensure the website is accessible"
},
{
"module": "dns",
"severity": "medium",
"title": "No DKIM record found",
"description": "None of the common DKIM selectors returned a valid key. Email authentication may be incomplete.",
"recommendation": "Configure DKIM signing with your email provider and publish the public key in DNS"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "ssl",
"severity": "high",
"title": "SSL certificate not found",
"description": "Could not retrieve SSL certificate",
"recommendation": "Ensure the site has a valid SSL certificate installed"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "mobile",
"severity": "high",
"title": "Missing viewport meta tag",
"description": "No viewport meta tag found — page will not be mobile-responsive",
"recommendation": "Add <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "rate-limits",
"severity": "medium",
"title": "No rate limiting detected",
"description": "10 rapid requests all succeeded without any rate-limit headers or 429 responses. The site may be vulnerable to abuse.",
"recommendation": "Implement rate limiting (e.g., 429 Too Many Requests) to protect against brute-force attacks"
},
{
"module": "layout-scan",
"severity": "medium",
"title": "No landmark elements",
"description": "No semantic landmarks found (nav, main, header, footer)",
"recommendation": "Use semantic HTML5 landmarks for better accessibility and SEO"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "uptime-checker",
"severity": "medium",
"title": "Intermittent failures",
"description": "1 of 3 requests failed",
"recommendation": "Investigate server stability — intermittent failures hurt user experience and SEO"
},
{
"module": "uptime-checker",
"severity": "medium",
"title": "Inconsistent www handling",
"description": "Both www and non-www versions respond with 200 — one should redirect to the other",
"recommendation": "Choose either www or non-www as canonical and redirect the other with a 301"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
},
{
"module": "cookies",
"severity": "high",
"title": "Module failed",
"description": "fetch failed",
"recommendation": "Try scanning again"
}
]
}
```Recommandations pour votre secteur
- 1Assurer la conformité aux normes d'accessibilité WCAG 2.1 AA
- 2Mettre en place tous les en-têtes de sécurité recommandés
- 3Vérifier que le sitemap couvre toutes les pages clés
- 4Optimiser le temps de chargement des pages à moins de 2 secondes
- 5Garantir un affichage parfaitement responsive sur toutes les pages
Liste de contrôle SEO pour Général
Conseils pour les sites de type Mixte
- →Créez des pages de destination ciblées pour chaque audience
- →Appliquez des métadonnées distinctes par groupe de pages
- →Segmentez votre sitemap par typologie de contenu
Contexte SEO local
L'Italie privilégie les contenus locaux avec une adoption massive des smartphones.
Utilisez Ctrl+P / Cmd+P pour enregistrer au format PDF