halbacharray.com

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

Google result

h

halbacharray.comhalbacharray.com/blog/sourcing-custom-halbach-arrays

Sourcing Custom Halbach Arrays from China: A Buyer's QA Gui…

A procurement guide for sourcing precision magnetic assemblies. Learn how to validate OEM capability, 3D Gauss mapping, and angular tolerances.

• Title · 125 characters — long titles get cut around 60
• Description · 143 characters

Fine-tune this snippet in the SERP simulator

Shared link card

halbacharray.com

Sourcing Custom Halbach Arrays from China: A Buyer's QA Guide | Halbach Array | Custom Halbach Arrays and Magnetic Assemblies

A procurement guide for sourcing precision magnetic assemblies. Learn how to validate OEM capability, 3D Gauss mapping, and angular tolerances.

• Open Graph image present

• Clear signalStructure

  Every section repeats the same Question/Standard template, which reads as formulaic

  Evidence

  • “Buyer Audit Question:”×2body
  • “The OEM Standard:”×2body
  Try this

  Vary section formats and add a real case, such as a rejected batch with measured numbers.

• Worth notingTone

  Generic 'insider' framing with no named author or first-hand anecdote

  Evidence

  • “we share an insider's technical checklist”body
  Try this

  Name the engineer who wrote it and include a specific supplier-audit story.

Signals of human authorship the page is doing well.

• Content

  Concrete technical specifics such as N52SH grade, a 1.5° rejection threshold and Helmholtz coil sorting show real domain knowledge.

• Words1,058
• Images11
• Alt coverage73%
• Images without size0
• Internal links55
• External links2
• Schema blocks1
• HTML size161 KB
• Text-to-HTML5%

Each bar is one sentence of the page, in reading order — taller means longer. Human prose tends to look jagged, mixing short punches with long explanations. Machine drafts tend to flatten into even bars.

• 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, 8 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 · 161 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

  1 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

  3 missing 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.