injectionmagnets.com

How the page presents itself in a Google result and as a shared link, rebuilt from the tags we crawled.

Google result

i

injectionmagnets.cominjectionmagnets.com/solutions/heavy-rare-earth-free-magnetic-components

Heavy-Rare-Earth-Free Magnetic Components | Injection Magne…

Heavy-Rare-Earth-Free Magnetic Components solution page with evaluation metrics, RFQ checklist, risk controls, buyer FAQ, and OEM validation support.

• Title · 61 characters — long titles get cut around 60
• Description · 149 characters

Fine-tune this snippet in the SERP simulator

Shared link card

injectionmagnets.com

Heavy-Rare-Earth-Free Magnetic Components | Injection Magnets

Heavy-Rare-Earth-Free Magnetic Components solution page with evaluation metrics, RFQ checklist, risk controls, buyer FAQ, and OEM validation support.

• Open Graph image present

• Strong signalContent

  Generated-looking keyword frame repeated in multiple sections, with awkward grammar from template substitution

  Evidence

  • “is most relevant when best for procurement and engineering teams that need a practical magnet design path”body
  • “Where Heavy-Rare-Earth-Free Magnetic Components fits”H3
  Try this

  Rewrite the templated fit paragraphs in plain language that names the specific buyer role and product constraint.

• Clear signalStructure

  Ten H2 sections follow a generic solution-page sequence with no page-specific ordering

  Evidence

  • “Solution Highlights”H2
  • “Application Evaluation Matrix”H2
  • “Buyer FAQ”H2
  Try this

  Reorder or merge sections around this material's actual buyer questions, and drop headings that exist only for template completeness.

Signals of human authorship the page is doing well.

• Content

  Specific technical references such as SmFeN, bonded NdFeB, and PPS engine-bay targets point to real product knowledge.

• Words664
• Images7
• Alt coverage100%
• Images without size0
• Internal links41
• External links3
• Schema blocks4
• HTML size133 KB
• Text-to-HTML4%

• Meta tags

  All present

  Why this matters

  Why it matters. Title and description are the two strings Google shows in search results. They decide whether anyone clicks. A canonical tag tells Google which URL is the source of truth when the same content lives at multiple paths.

  Passing looks like. A title, a meta description and a canonical link are all present, with exactly one description tag, placed where Google reads it. Their lengths are shown in the report's search preview.

  Fix. Add the missing tags inside the page head and delete any second description tag. Keep images and iframes below your meta tags, because Google stops reading the head at the first one. Treat the title as a headline you'd want to read in a SERP, not a brand slogan.

• Heading structure

  1 H1, 10 H2

  Why this matters

  Why it matters. Headings are how crawlers and assistive tech understand a page's outline. One H1 names the page. H2s break it into sections. A missing H1, or several, blurs what the page is about.

  Passing looks like. Exactly one H1, and at least one H2.

  Fix. Replace the missing or duplicate H1 with a single, descriptive heading. Promote section titles to H2. Demote sub-points to H3.

• Mobile readiness

  Responsive

  Why this matters

  Why it matters. Google indexes the mobile version of a page. Without a responsive viewport, phones render the page zoomed out, which makes it hard to read and use.

  Passing looks like. A viewport meta tag set to width=device-width. The scan reads the HTML and doesn't render the page, so it can't check touch targets or font sizes.

  Fix. Add a viewport meta tag set to width=device-width and initial-scale=1, then audit your largest blocks at mobile widths.

• Page speed signals

  0.5s · 133 KB

  Why this matters

  Why it matters. Response time, page weight and images that load without a reserved size all show up in Core Web Vitals. Slow pages, and layouts that jump as images arrive, cost visitors and rankings.

  Passing looks like. The HTML arrives in under 1.5 s and weighs under 500 KB, the page has fewer than 30 images, and no more than two images lack width and height. These are signals from one HTML fetch, not a PageSpeed Insights measurement.

  Fix. Speed up the server response and trim the HTML. Give every image width and height attributes, or a CSS aspect-ratio, so the layout doesn't jump, and serve compressed images sized to the viewport.

• Schema markup

  4 schema blocks

  Why this matters

  Why it matters. JSON-LD structured data is how you earn rich results: review stars, FAQ accordions, breadcrumbs, article cards. Skip it and Google has nothing structured to pull from when it builds your SERP card.

  Passing looks like. At least one JSON-LD block is present. The check doesn't validate the block or its types, so test it with Google's Rich Results Test too.

  Fix. Add an application/ld+json script block describing the page. Validate with Google's Rich Results Test before deploying.

• Broken links

  0/5 broken in sample

  Why this matters

  Why it matters. Broken internal links waste crawl budget, degrade UX, and signal to Google that the site isn't well-maintained. They also cap how deep crawlers reach.

  Passing looks like. Every internal link in the sample loads successfully, after following redirects. Timeouts and network errors count as broken.

  Fix. Use the link list above to spot the broken paths. Either restore the missing pages or update the links to point at live URLs.

• Image alt text

  All have alt

  Why this matters

  Why it matters. Alt text is what screen readers read aloud, and what Google reads instead of pixels. Skip it and you lose on both fronts.

  Passing looks like. Nearly every image has non-empty alt text. An empty alt="" counts as missing here, even on a decorative image.

  Fix. Audit images in /assets and CMS uploads. Write alts that describe what's in the image, not what it links to.

Every H1, H2, and H3 we found on the page, in document order.

We HEAD-check up to five internal links to spot broken paths quickly.