5 ship-blockers, 32 should-fix
Heuristic score over 33 sampled pages, not Google's classifier. How to read this ↓
These rules still ran and emitted findings: the site-type profile lowered their severity so the score reflects how the signal applies to this kind of site, not a one-size-fits-all penalty.
aeo/answer-firstaeo/citable-factsaeo/freshness-signalscontent/heading-structurespam/thin-contenttech/og-completenessSave this audit to your history, sign in.
Monitor this domain with Pro →Your origin handled the crawl cleanly. Under Googlebot / AI-crawler bursts you should be fine.
content/image-attributeswarningstructural26 pageshttps://networkpulse.fr/: 21 of 21 <img> tags declare neither width/height attributes nor inline sizing (e.g. /content/images/2025/08/networkpulse-logo-clair-transparent1.webp, /content/images/2026/01/networkpulse-logo-blanc-transparent-1.webp, /content/images/2026/01/networkpulse-logo-blanc-transparent-1.webp). Without an aspect ratio the browser cannot reserve space, so content shifts as each image loads, which is what Cumulative Layout Shift measures.
spam/near-duplicatecriticalstructural4 pages2 pages form a near-duplicate cluster (85.9–85.9% similar).
links/orphan-pageserrormoderate2 pageshttps://networkpulse.fr/page/2 has no inbound links from other pages in this crawl.
content/unique-valueerrorstructural1 pagehttps://networkpulse.fr/tag/logiciels has low unique-content density 0.115 (11.5% of its 38 distinct words are page-distinctive; floor 0.20). Most of its vocabulary also appears on other pages.
content/meta-description-presencewarningmoderate3 pageshttps://networkpulse.fr/contact has no meta description, so Google will compose the snippet itself from page text, so you lose control over the SERP pitch and likely CTR.
2 pages form a near-duplicate cluster (85.9–85.9% similar).
2 pages form a near-duplicate cluster (85.9–85.9% similar). Shared: installation docker détaillée... (3w), auto-hébergement par guillaume... (5w), 21, 2026 puremac... (29w). Unique: 240w of 1140w. Differentiate these pages by adding unique content to each.
https://networkpulse.fr/page/2 has no inbound links from other pages in this crawl.
↗ networkpulse.fr/page/2Link to this page from a relevant hub or index page, and include it in your site navigation.
https://networkpulse.fr/tag/logiciels has low unique-content density 0.115 (11.5% of its 38 distinct words are page-distinctive; floor 0.20). Most of its vocabulary also appears on other pages.
↗ networkpulse.fr/tag/logicielsRaise originality density: add page-specific text, a distinct lead, this record's own facts, page-specific examples. Content repeated across pages on the same axis (boilerplate, shared legal/spec blocks, per-axis data like a role's regulations across that role's documents) is common vocabulary and does NOT raise density, even when it is useful.
https://networkpulse.fr/: 21 of 21 <img> tags declare neither width/height attributes nor inline sizing (e.g. /content/images/2025/08/networkpulse-logo-clair-transparent1.webp, /content/images/2026/01/networkpulse-logo-blanc-transparent-1.webp, /content/images/2026/01/networkpulse-logo-blanc-transparent-1.webp). Without an aspect ratio the browser cannot reserve space, so content shifts as each image loads, which is what Cumulative Layout Shift measures.
↗ networkpulse.fr/Set the intrinsic width and height attributes on each <img> and let CSS scale it (width: 100%; height: auto). The browser derives aspect-ratio from the attribute pair and reserves the box before the bytes arrive. In a template, bind both from the same data source as the src.
https://networkpulse.fr/contact has no meta description, so Google will compose the snippet itself from page text, so you lose control over the SERP pitch and likely CTR.
↗ networkpulse.fr/contactAdd <meta name="description" content="..."> to <head> with a summary written for THIS page (not a site-wide boilerplate line).
2 crawlable page(s) not in sitemap.
Add these pages to your sitemap.xml to ensure Google discovers them.
https://networkpulse.fr/llms.txt exists but is malformed: file does not start with an `# ` H1 title.
Ensure https://networkpulse.fr/llms.txt opens with an "# Site Name" H1, has at least one "## Section" heading, and lists pages as "- [Title](https://...): short description". See https://llmstxt.org.
https://networkpulse.fr/contact has a title of only 7 characters ("Contact"), which reads like a template field that was never filled in.
↗ networkpulse.fr/contactBind the page's own entity into the title. Google documents replacing the title link when part of the title text is missing (its example is the literal "| Site Name"), so a near-empty title gets rewritten from the H1 or anchor text. There is no documented upper limit, so nothing here asks you to shorten a title.
https://networkpulse.fr/ has 1 unique citable fact. AI Overviews cite specific numbers and named references.
↗ networkpulse.fr/Replace vague language ("varies", "several weeks", "affordable", "many options") with specific values a reader or AI engine would cite: exact prices, percentages, dates, timeframes, version numbers, named products, standards, or regulations that apply to this page. For pSEO templates, bind these values from your data source so each page gets entity-specific numbers instead of repeating the same template wording. Target: 8+ unique facts per page.
https://networkpulse.fr/ reads as FAQ content (2 question-style headings (e.g. "DMZ réseau : Qu'est-ce que c'est et pourquoi c'est indispensable à votre sécurité ?", "igloohome Keybox 3 : La meilleure boîte à clés connectée ?")) but carries no machine-readable question/answer pairs.
↗ networkpulse.fr/Fix this in the visible page, not in markup: give each question its own heading and put the complete answer in the first paragraph directly beneath it, so an answer engine can lift a whole question/answer pair without reassembling it. Do NOT add FAQPage JSON-LD expecting a rich result: Google removed the FAQ rich result from Search on 2026-05-07 and deleted its documentation on 2026-06-15, and QAPage is documented as being only for pages where users can submit answers, not for a site's own FAQ. If a non-Google consumer of your schema needs the markup, generate it from the same per-record data that renders the headings: don't ship identical questions with only the entity name swapped.
https://networkpulse.fr/ was last updated 187 days ago (threshold: 180). Some pages are evergreen by design: only act if this page's information changes over time.
↗ networkpulse.fr/AI engines prioritize fresh content for citation. If the page is still accurate, refresh the visible date and bump dateModified. If information has changed, update the body accordingly.
https://networkpulse.fr/contact serves 6 images and not one uses srcset or <picture>, so phones download the desktop-sized file. Google recommends responsive images; this is guidance rather than a requirement, and no image dimension or byte limit is documented.
↗ networkpulse.fr/contactEmit a srcset with a handful of widths plus a sizes attribute, or wrap the img in <picture> to offer a modern format with a fallback. Most image CDNs and framework Image components generate both from one source URL.
https://networkpulse.fr/contact has thin content (22 words).
Add at least 278 more words of substantive content relevant to this page's specific topic.
https://networkpulse.fr/contact does not open with a direct, extractable answer: no specific numbers, dates, or dollar amounts
↗ networkpulse.fr/contactRestructure the template to open with entity-specific facts. Instead of boilerplate or a topic preamble, lead with a complete-answer sentence containing the key number, date, agency, or form name a reader (or AI Overview) would cite. Target: <100 words, at least one concrete number, at least one named entity.
https://networkpulse.fr/author/guillaume is missing Open Graph tags: og:image.
↗ networkpulse.fr/author/guillaumeAdd the missing meta tags inside <head>: <meta property="og:image" content="...">.
https://networkpulse.fr/ has no <h1> element.
↗ networkpulse.fr/Add a single <h1> that names the page's primary topic. Google uses H1 to disambiguate when the title tag is unclear.
Is this your site?
Claim it to manage the listing, get a verified badge, and a followed backlink.
networkpulse.fr passed the audit. Embed the badge on your site or README; it always shows your current grade.
[](https://pseolint.dev/r/ZZg67a3jhy)<a href="https://pseolint.dev/r/ZZg67a3jhy"><img src="https://pseolint.dev/api/badge/networkpulse.fr" alt="pseolint grade for networkpulse.fr" /></a>sitemap.xml as the source of truth. Pro lifts the budget to 500 pages on manual re-audits and crawls beyond the sitemap.