Most structured data parsers miss JSON-LD inside @graph blocks, audit finds

·4 views

A developer discovered that nine out of twelve structured data audit tools, including their own, fail to detect schema markup when it is wrapped inside a JSON-LD @graph block rather than a flat top-level object. The @graph format is the default output of popular WordPress SEO plugins Yoast SEO and RankMath, meaning a large share of correctly marked-up web pages are being misread as having no structured data. Unlike flat JSON-LD, the @graph structure allows schema nodes to reference each other by ID, forming a single linked entity graph rather than isolated, redundant blocks. The author identified the bug in their own tool after a well-marked page returned a zero schema score, and traced the root cause to parsers checking only for a top-level @type field. A fix involving recursive node iteration — handling both flat and @graph shapes at the parse boundary — is proposed so that no downstream check needs to account for either format separately.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Integrate st-core.fscss CSS Charts into a Svelte App at Build Time

The st-core.fscss library renders charts using pure CSS clip-path polygons and custom properties, requiring no JavaScript chart library, SVG, or canvas. Integrating it into a Svelte or SvelteKit project involves compiling the FSCSS source file into static CSS once at build time using the FSCSS CLI, rather than loading a runtime CDN script on every page load. Svelte's role is limited to reactively mapping data values to CSS custom properties such as --st-p1 and --st-p2, while the browser handles rendering via the compiled CSS. A key constraint is that the array length defined in the FSCSS template must match the number of data points, as it determines the polygon geometry and cannot be changed without recompiling. The article provides component examples for both Svelte 4 and Svelte 5, along with package.json scripts to automate compilation before each build.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer stress-tests AI cost-monitoring agent using chaos testing and red teaming

A software developer subjected their AWS cost-monitoring AI agent, built on Amazon Bedrock's AgentCore Runtime using the Strands framework, to deliberate failure and adversarial testing. The agent, which daily reads AWS billing data and emails a color-coded spending report, had never been tested under adverse conditions such as API timeouts, partial data returns, or prompt manipulation. Using Strands Evals 1.0, which shipped chaos testing and red-teaming tools in June, the developer built an isolated lab replica of the agent running on fixture data to avoid incurring real API costs during testing. The key concern was not outright crashes but silent, believable failures — such as a falsely reassuring green-status report while cloud costs quietly escalate. The developer's stated goal is to share replicable testing methods so others can apply the same adversarial evaluation approach to their own AI agents.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Launches Free AI Toolkit for LinkedIn Profiles, Resumes, and Bios

A developer has released ProfileCraftAI, a free, no-signup toolkit designed to help users write LinkedIn headlines, resume summaries, professional bios, and more. The platform offers eight tools in total, built using Next.js for the frontend and Groq's Llama-based API for near-instant text generation, deployed on Vercel. The project was motivated by the developer's observation that many people struggle to articulate their professional identity in writing. Key lessons from the build include the importance of carefully structured prompts to avoid generic AI output, adding educational content alongside each tool to build user trust, and implementing rate limiting early to prevent abuse. The toolkit is publicly accessible at profilecraftai.com, and the developer is actively seeking community feedback on usability and missing features.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Disposable Email Checkers Protect Sender Reputation and Block Signup Abuse

Disposable email addresses pose a significant risk to businesses running SaaS products, newsletters, or waitlists, as these inboxes typically expire within hours and cause hard bounces that damage a sender's domain reputation. Sustained bounce rates above roughly 2% can cause mailbox providers to route all outgoing mail — including legitimate messages — to spam folders. Tools like Reloop's free Temp Email Checker address this by matching signup addresses against a catalogue of approximately 210,000 known disposable providers, validating MX records, and flagging role-based prefixes, all without probing actual mailboxes. Beyond deliverability, blocking disposable emails at the point of registration also prevents free-trial farming, coupon fraud, waitlist inflation, and multi-account bot abuse. The recommended approach is to validate email addresses before they enter a database, then immediately suppress any hard bounces to prevent dead addresses from receiving follow-up sends.

0 comments Read more at DEV Community