{"slug": "simple-alternative-method-to-pass-ard-manifest-validation-in-google-pagespeed", "title": "Simple Alternative Method to Pass ARD Manifest Validation in Google PageSpeed Insights & Lighthouse", "summary": "A developer published a step-by-step guide showing that a minimal two-line JSON file containing an empty \"entries\" array, placed at /.well-known/ard.json, can satisfy Lighthouse's new \"ARD manifest is valid\" audit under the Agentic Browsing category. The approach exploits the ARD v0.91 specification, dated August 26, 2026, which requires a top-level entries array but not that it contain any resources, so the empty array passes schema validation without advertising any MCP servers, A2A agents, or other capabilities. The guide cautions that the shortcut only satisfies the structural check and is not a substitute for real Agentic Resource Discovery.", "body_md": "If you've recently tested your website using **Google PageSpeed Insights or Lighthouse**, you may have noticed a new check under the **Agentic Browsing** category called **“ARD manifest is valid.”**\n\nHere's a quick way to satisfy this validation using a minimal JSON file, without installing plugins or configuring complex agentic services.\n\n**Step 1:** Log in to your website's hosting control panel (cPanel, DirectAdmin, or similar).\n\n**Step 2:** Open File Manager and navigate to your website's document root, typically:\n\n`public_html/`\n\n**Step 3:** Look for a folder named:\n\n`.well-known`\n\nIf this folder doesn't exist, **create a new folder** with exactly that name, including the dot (`.`) at the beginning.\n\n💡 *Tip: Enable “Show Hidden Files” in File Manager if you cannot see the `.well-known` folder.*\n\n**Step 4:** Inside the `.well-known` folder, create a file named:\n\n`ard.json`\n\nYour final file path should look like this:\n\n`public_html/.well-known/ard.json`\n\n**Step 5:** Open the file and paste the following JSON:\n\n```\n{\n  \"entries\": []\n}\n```\n\nSave the file.\n\n**Step 6:** Open the following URL in your browser:\n\n`https://yourdomain.com/.well-known/ard.json`\n\nReplace `yourdomain.com` with your actual domain.\n\nYou should see the JSON content without a 404, 403, or other error.\n\n**Step 7:** Run your website through PageSpeed Insights or Lighthouse again and check the ARD manifest validation result.\n\nThis simple approach is suitable when:\n\nThe empty `entries` array is allowed by the current ARD manifest schema and can pass Lighthouse's validation.\n\nAvoid this shortcut when:\n\nFor these cases, you should create a proper ARD manifest with resource identifiers, names, media types, endpoints, and relevant discovery information.\n\n**An empty manifest does not advertise any resources.** It only provides a valid manifest structure.\n\nEven with correct JSON, validation may fail or the audit may not recognize your file if:\n\n`ai-catalog.json` location.\nIf your website uses a custom document root or a different hosting architecture, place the file wherever it becomes publicly accessible at `/.well-known/ard.json`.\n\n**ARD stands for Agentic Resource Discovery.**\n\nGoogle announced the ARD specification on **June 17, 2026**, to help AI agents and registries discover and verify capabilities published across the web.\n\nARD can describe resources such as MCP servers, A2A agents, agent skills, and other tools or services.\n\nAn ARD manifest is normally published at:\n\n`/.well-known/ard.json`\n\nThe ARD v0.91 specification, dated August 26, 2026, requires a top-level `entries` array but does not require that array to contain any entries.\n\n**Lighthouse support:**\n\n`rel=\"ard\"` while retaining legacy compatibility.\nThis explains why an empty `entries` array can pass schema validation: it is a valid array containing zero resource declarations.\n\nPassing the ARD manifest audit does **not** mean:\n\nAlso, if no ARD manifest is published or advertised, Lighthouse may simply mark the audit as **Not Applicable**, which is not necessarily an error.\n\nThis method is useful for basic manifest validation, not as a substitute for actual agentic resource discovery.\n\n**Sometimes, a two-line JSON file is enough to satisfy a technical validation check. Just understand what you're validating!** 🚀", "url": "https://wpnews.pro/news/simple-alternative-method-to-pass-ard-manifest-validation-in-google-pagespeed", "canonical_source": "https://dev.to/radditollc/simple-alternative-method-to-pass-ard-manifest-validation-in-google-pagespeed-insights-lighthouse-562a", "published_at": "2026-11-15 05:15:14+00:00", "updated_at": "2026-11-15 05:22:05.416810+00:00", "lang": "en", "topics": ["agent-protocols", "ai-agents", "developer-tools"], "entities": ["Google", "Lighthouse", "PageSpeed Insights", "ARD", "MCP", "A2A"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/simple-alternative-method-to-pass-ard-manifest-validation-in-google-pagespeed", "markdown": "https://wpnews.pro/news/simple-alternative-method-to-pass-ard-manifest-validation-in-google-pagespeed.md", "text": "https://wpnews.pro/news/simple-alternative-method-to-pass-ard-manifest-validation-in-google-pagespeed.txt", "jsonld": "https://wpnews.pro/news/simple-alternative-method-to-pass-ard-manifest-validation-in-google-pagespeed.jsonld"}}