<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Hieu Le</title>
    <description>The latest articles on DEV Community by Hieu Le (@hieu_le_f3630aa13143b35d8).</description>
    <link>https://dev.to/hieu_le_f3630aa13143b35d8</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3714028%2F57cbe114-3ab6-4f40-9762-0814e0c7a064.png</url>
      <title>DEV Community: Hieu Le</title>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hieu_le_f3630aa13143b35d8"/>
    <language>en</language>
    <item>
      <title>jQuery Outdated Version Security: How to Upgrade Safely</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Fri, 20 Nov 2026 08:53:21 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/jquery-outdated-version-security-how-to-upgrade-safely-3g83</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/jquery-outdated-version-security-how-to-upgrade-safely-3g83</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/jquery-outdated-version-security" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;An outdated jQuery version can expose a page to cross-site scripting when vulnerable code handles attacker-controlled content. In the Sitecheckly survey, 31% of the 680 sites exposing a jQuery version still run jQuery 1.x or 2.x. Find every loaded copy, check its advisories, and upgrade with jQuery Migrate and regression tests.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which jQuery versions are outdated?
&lt;/h2&gt;

&lt;p&gt;“Outdated” is a starting point, not a complete security assessment. Separate these questions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Is the release still supported?&lt;/strong&gt; An end-of-life branch no longer receives normal maintenance.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does the exact version have a known vulnerability?&lt;/strong&gt; Match it against the affected versions in an advisory.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does your code meet the conditions for exploitation?&lt;/strong&gt; Review how the application uses the affected APIs.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For jQuery 1.x security concerns or questions about jQuery 2.x end of life, start with the &lt;a href="https://endoflife.date/jquery" rel="noopener noreferrer"&gt;jQuery lifecycle listing&lt;/a&gt;. Check the current support status before selecting an upgrade target. Do not assume that any release labeled “newer” is a suitable long-term destination.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Survey scope and method.&lt;/strong&gt; The finding above comes from the October 2026 Sitecheckly survey of the Tranco top 10,000, using Tranco list 7462X. The ranking covers 2026-10-02 to 2026-10-31. Home pages were fetched on 2026-11-01. Of 10,000 domains, 4,934 could be analyzed. The remainder were mostly CDN, DNS and API hosts, sites whose robots.txt rules asked crawlers to stay away, or sites that blocked automated requests. See the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;survey methodology&lt;/a&gt; and &lt;a href="https://sitecheckly.com/blog/website-security-statistics-october-2026" rel="noopener noreferrer"&gt;related security results&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;That finding describes detected versions on the analyzed home pages. It is not evidence that those sites were exploited, and it is not an inventory of every page or dependency they contain.&lt;/p&gt;

&lt;h2&gt;
  
  
  What security risks do old jQuery versions create?
&lt;/h2&gt;

&lt;p&gt;The main question is not simply whether jQuery is old. It is whether an affected operation processes input an attacker can influence.&lt;/p&gt;

&lt;p&gt;These advisories illustrate why the version and the code path both matter:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Advisory&lt;/th&gt;
&lt;th&gt;Relevant behavior&lt;/th&gt;
&lt;th&gt;What to investigate&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2" rel="noopener noreferrer"&gt;CVE-2020-11022&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Passing untrusted HTML to affected DOM manipulation methods can execute untrusted code. The fix was released in jQuery 3.5.0.&lt;/td&gt;
&lt;td&gt;Find code that passes HTML strings to methods such as &lt;code&gt;.html()&lt;/code&gt; or &lt;code&gt;.append()&lt;/code&gt;. Trace where those strings originate.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6" rel="noopener noreferrer"&gt;CVE-2020-11023&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Affected DOM manipulation involving HTML containing &lt;code&gt;&amp;lt;option&amp;gt;&lt;/code&gt; elements can execute untrusted code. The fix was released in jQuery 3.5.0.&lt;/td&gt;
&lt;td&gt;Review dynamic HTML creation, including select controls populated from external or user-controlled content.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2015-9251" rel="noopener noreferrer"&gt;CVE-2015-9251&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Affected cross-domain Ajax requests can execute a script response when the data type is not specified.&lt;/td&gt;
&lt;td&gt;Check the exact affected range and conditions in the advisory, then review cross-domain requests and their expected response types.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The fixes in jQuery 3.5.0 address the listed DOM manipulation vulnerabilities. That does not make that release the recommended upgrade destination today. Select a currently supported release and review the compatibility work needed to reach it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A vulnerable version is not proof of a compromise.&lt;/strong&gt; For each finding, record:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The detected version and where it loads.&lt;/li&gt;
&lt;li&gt;The advisory that applies to it.&lt;/li&gt;
&lt;li&gt;The affected API calls in your code or dependencies.&lt;/li&gt;
&lt;li&gt;Whether attacker-controlled input can reach those calls.&lt;/li&gt;
&lt;li&gt;The planned dependency update and its owner.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Use this review to prioritize work. Do not use an incomplete search for vulnerable calls as a reason to leave an unsupported dependency indefinitely.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you find the jQuery version on your page?
&lt;/h2&gt;

&lt;p&gt;Start with the page where the problem was reported. Open the browser’s developer tools and run this in the console:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nb"&gt;window&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;jQuery&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;window&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;jQuery&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;fn&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;jquery&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This checks the version exposed through the current global &lt;code&gt;jQuery&lt;/code&gt; object. It is not a complete dependency inventory. Multiple copies or code that changes ownership of the global object can make a single console check incomplete. The &lt;a href="https://jquery.com/upgrade-guide/3.0/" rel="noopener noreferrer"&gt;official upgrade guide&lt;/a&gt; covers version checks and compatibility considerations.&lt;/p&gt;

&lt;p&gt;Next, inspect the page’s script requests and your application’s dependency files:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Look for standalone jQuery assets and bundled dependencies.&lt;/li&gt;
&lt;li&gt;Trace each copy to the application, theme, plugin or build configuration that supplies it.&lt;/li&gt;
&lt;li&gt;Record which pages and features depend on that copy.&lt;/li&gt;
&lt;li&gt;Check important pages separately rather than assuming they use the home page’s scripts.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep a short inventory:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Page or feature&lt;/th&gt;
&lt;th&gt;Detected version&lt;/th&gt;
&lt;th&gt;Provided by&lt;/th&gt;
&lt;th&gt;Update owner&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Home page&lt;/td&gt;
&lt;td&gt;Record the result&lt;/td&gt;
&lt;td&gt;Application, theme or plugin&lt;/td&gt;
&lt;td&gt;Assign an owner&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Contact form&lt;/td&gt;
&lt;td&gt;Check separately&lt;/td&gt;
&lt;td&gt;Form integration&lt;/td&gt;
&lt;td&gt;Assign an owner&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Account area&lt;/td&gt;
&lt;td&gt;Check separately&lt;/td&gt;
&lt;td&gt;Application bundle&lt;/td&gt;
&lt;td&gt;Assign an owner&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;For an external check of the entered page, use the &lt;a href="https://sitecheckly.com/tools/vulnerable-js-library-scanner" rel="noopener noreferrer"&gt;free vulnerable JS library scanner&lt;/a&gt;. For a broader passive check of that URL, &lt;a href="https://sitecheckly.com/security-audit" rel="noopener noreferrer"&gt;run a security audit&lt;/a&gt;. Sitecheckly is free, requires no sign-up, and audits one page per run. Its security audit is separate from the home page’s SEO and AEO scan.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you upgrade jQuery safely?
&lt;/h2&gt;

&lt;p&gt;Treat the update as a dependency change, not a file swap.&lt;/p&gt;

&lt;h3&gt;
  
  
  Prepare a staging copy
&lt;/h3&gt;

&lt;p&gt;Before changing production:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Back up the application and its configuration.&lt;/li&gt;
&lt;li&gt;Create a staging copy that includes the affected features.&lt;/li&gt;
&lt;li&gt;List plugins and custom scripts that depend on jQuery.&lt;/li&gt;
&lt;li&gt;Record the current behavior of critical user journeys.&lt;/li&gt;
&lt;li&gt;Identify how you will restore the previous deployment if testing misses a problem.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Choose the target release based on current support status and compatibility requirements, not merely the first version that clears a particular advisory.&lt;/p&gt;

&lt;h3&gt;
  
  
  Use jQuery Migrate to find compatibility problems
&lt;/h3&gt;

&lt;p&gt;Follow the &lt;a href="https://jquery.com/upgrade-guide/3.0/" rel="noopener noreferrer"&gt;official jQuery upgrade guide&lt;/a&gt; for your starting version. Use the matching jQuery Migrate plugin and follow any staged upgrade steps it requires.&lt;/p&gt;

&lt;p&gt;Migrate helps identify or preserve deprecated behavior during an upgrade. &lt;strong&gt;It does not patch an old jQuery release or replace a patched dependency.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Work through its warnings in staging. For each warning, identify whether the fix belongs in your code or in a plugin. Resolve the underlying compatibility issue rather than treating the absence of visible breakage as sufficient evidence that the upgrade is complete.&lt;/p&gt;

&lt;h3&gt;
  
  
  Update the dependency at its source
&lt;/h3&gt;

&lt;p&gt;If a theme or plugin supplies jQuery, first look for a maintained update to that package. If your build manages the dependency, update it through that process.&lt;/p&gt;

&lt;p&gt;Avoid manually replacing a managed file without checking how future updates will affect it. Make the change reproducible, and record where the version is controlled so the next deployment does not silently undo your work.&lt;/p&gt;

&lt;h3&gt;
  
  
  Test behavior, then verify the deployment
&lt;/h3&gt;

&lt;p&gt;Use a targeted regression checklist:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Area&lt;/th&gt;
&lt;th&gt;What to test&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Forms&lt;/td&gt;
&lt;td&gt;Validation, submission, error messages and success states&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Navigation&lt;/td&gt;
&lt;td&gt;Menus, dropdowns, mobile controls and keyboard interaction&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ajax flows&lt;/td&gt;
&lt;td&gt;Loading, successful responses, empty results and failures&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dynamic HTML&lt;/td&gt;
&lt;td&gt;Dialogs, tabs, inserted content and populated select controls&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Plugin features&lt;/td&gt;
&lt;td&gt;Every important interaction provided by a dependent plugin&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;When compatibility work is complete, retest without Migrate. After deployment, confirm the version actually served on each affected page. Remove unnecessary duplicate copies only after checking their dependencies, then repeat the important user journeys.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should you do if an upgrade is blocked?
&lt;/h2&gt;

&lt;p&gt;Make the blocker explicit. Record the dependency, its owner, the feature it supports and the action needed to replace or update it. Ask the maintainer for a compatible release, or evaluate a maintained alternative.&lt;/p&gt;

&lt;p&gt;While that work proceeds, review the exposed code paths:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Untrusted HTML:&lt;/strong&gt; Trace content passed into DOM manipulation methods. Restrict risky inputs and use context-appropriate output handling. Check your assumptions against the conditions in the &lt;a href="https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2" rel="noopener noreferrer"&gt;HTML prefilter advisory&lt;/a&gt; and the &lt;a href="https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6" rel="noopener noreferrer"&gt;DOM manipulation advisory&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cross-domain Ajax:&lt;/strong&gt; Review destinations, expected response types and requests without an explicit data type. Compare them with the affected versions and conditions in &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2015-9251" rel="noopener noreferrer"&gt;CVE-2015-9251&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Defense in depth:&lt;/strong&gt; Consider a Content Security Policy, testing its effects before enforcement. The &lt;a href="https://sitecheckly.com/blog/content-security-policy-example-report-only" rel="noopener noreferrer"&gt;CSP Report-Only guide&lt;/a&gt; provides a practical starting point. CSP is not a guarantee against XSS and does not repair a vulnerable library.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These measures can reduce exposure while you remove the blocker. They are not substitutes for patching.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do next&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Identify every jQuery copy on the affected page and who supplies it.&lt;/li&gt;
&lt;li&gt;Match each version to its lifecycle status and relevant advisories.&lt;/li&gt;
&lt;li&gt;Assign the upgrade, test it in staging, and verify the deployed result.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does jQuery Migrate patch security vulnerabilities?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Migrate helps identify or preserve deprecated behavior during an upgrade; it does not replace a patched jQuery release. See the &lt;a href="https://jquery.com/upgrade-guide/3.0/" rel="noopener noreferrer"&gt;upgrade guide&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a Content Security Policy replace a jQuery upgrade?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. A CSP can provide defense in depth, but it does not remove a vulnerable library or fix the affected code path. See the &lt;a href="https://sitecheckly.com/blog/content-security-policy-example-report-only" rel="noopener noreferrer"&gt;CSP guide&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does a vulnerable version mean my site has been hacked?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Exposure depends on the affected code path and the conditions in the relevant advisory. Investigate whether attacker-controlled input can reach it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why might checking one page miss an outdated copy?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Different pages can load different scripts or plugin assets. Audit representative pages separately and inspect the dependencies responsible for each copy.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>jquery</category>
      <category>javascript</category>
      <category>security</category>
      <category>upgrades</category>
    </item>
    <item>
      <title>Missing Security Headers: How to Check and Fix Them</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Thu, 19 Nov 2026 09:08:53 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/missing-security-headers-how-to-check-and-fix-them-42lo</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/missing-security-headers-how-to-check-and-fix-them-42lo</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/missing-security-headers" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Missing security headers are HTTP response headers absent from a page’s response that could instruct browsers to apply protections. Check the affected URL, add headers appropriate to your application, and test the response again. Sitecheckly found “Missing security headers” on 84% of the 103 sites audited in the last 90 days.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do missing security headers mean?
&lt;/h2&gt;

&lt;p&gt;The finding concerns the response for the URL tested. It does not establish that every page on the site has the same problem. Sitecheckly audits one page per run, so treat the result as a finding for that page.&lt;/p&gt;

&lt;p&gt;HTTP response security headers let a server communicate browser-facing policies. Depending on the header, those policies can limit content-type guessing, control referrer information, or require HTTPS for future connections. &lt;a href="https://developer.mozilla.org/en-US/docs/Web/Security/Practical_implementation_guides" rel="noopener noreferrer"&gt;MDN’s practical security implementation guides&lt;/a&gt; explain how these protections fit together.&lt;/p&gt;

&lt;p&gt;Start with the specific header names flagged in the report. An absent header is a reason to review the page’s configuration, not a reason to paste every available policy into production. Use the &lt;a href="https://sitecheckly.com/blog/security-headers-list-recommended-values" rel="noopener noreferrer"&gt;security headers list and recommended values&lt;/a&gt; to decide which policies fit your application.&lt;/p&gt;

&lt;p&gt;The survey figure above describes findings in Sitecheckly audits. It is not an estimate of how often the issue occurs across the entire web, and it does not show that every finding was exploitable.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you check a page for missing security headers?
&lt;/h2&gt;

&lt;p&gt;Enter the affected URL in the free &lt;a href="https://sitecheckly.com/tools/security-headers-checker" rel="noopener noreferrer"&gt;security headers checker&lt;/a&gt;. Review the returned header names and values, rather than relying only on a pass or fail label.&lt;/p&gt;

&lt;p&gt;For a separate passive check of the entered page, run a &lt;a href="https://sitecheckly.com/security-audit" rel="noopener noreferrer"&gt;Sitecheckly security audit&lt;/a&gt;. It is free, requires no sign-up, and audits one URL per run. It does not scan the whole site.&lt;/p&gt;

&lt;p&gt;Use this checking method before making changes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Record the exact URL.&lt;/strong&gt; Keep it for the verification run.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Follow the result through any redirects.&lt;/strong&gt; Inspect the final page response, not just the response that redirects to it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Record what is missing.&lt;/strong&gt; Keep a short list of the flagged header names and any values already present.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Find the configuration owner.&lt;/strong&gt; Identify whether the application, web server, reverse proxy, or CDN manages the response you are checking.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep the same page-level scope when interpreting the survey: a finding on a tested URL is not evidence that every URL on that site has identical headers.&lt;/p&gt;

&lt;p&gt;Before editing configuration, also check whether another layer already sets the headers. Apache’s documentation specifically describes how headers from different response tables and upstream applications can produce duplicates. Its &lt;a href="https://httpd.apache.org/docs/2.4/mod/mod_headers.html" rel="noopener noreferrer"&gt;mod_headers guidance&lt;/a&gt; is useful when tracing that problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you add security headers in Nginx?
&lt;/h2&gt;

&lt;p&gt;Add the following directives inside the existing &lt;code&gt;server&lt;/code&gt; or &lt;code&gt;location&lt;/code&gt; block that handles the affected URL:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nginx"&gt;&lt;code&gt;&lt;span class="n"&gt;add_header&lt;/span&gt; &lt;span class="no"&gt;X&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Content&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Type&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Options&lt;/span&gt; &lt;span class="s2"&gt;"nosniff"&lt;/span&gt; &lt;span class="n"&gt;always&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="n"&gt;add_header&lt;/span&gt; &lt;span class="nc"&gt;Referrer&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Policy&lt;/span&gt; &lt;span class="s2"&gt;"strict-origin-when-cross-origin"&lt;/span&gt; &lt;span class="n"&gt;always&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;These are starting-point policies, not a complete security configuration:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;X-Content-Type-Options: nosniff&lt;/code&gt;&lt;/strong&gt; tells browsers to respect the declared content type rather than reinterpret applicable responses through MIME sniffing. It does not correct an incorrect &lt;code&gt;Content-Type&lt;/code&gt;. See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options" rel="noopener noreferrer"&gt;MDN’s X-Content-Type-Options reference&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;Referrer-Policy: strict-origin-when-cross-origin&lt;/code&gt;&lt;/strong&gt; allows full referrer information for same-origin requests, limits eligible cross-origin requests to the origin, and omits the referrer on HTTPS-to-HTTP requests. See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy" rel="noopener noreferrer"&gt;MDN’s Referrer-Policy reference&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Review existing &lt;code&gt;add_header&lt;/code&gt; directives before applying the change. Placement matters. Under Nginx’s default inheritance behavior, adding an &lt;code&gt;add_header&lt;/code&gt; directive at a lower configuration level can prevent that level from inheriting the parent’s &lt;code&gt;add_header&lt;/code&gt; directives. The &lt;code&gt;always&lt;/code&gt; parameter applies the header regardless of the response code. Check the &lt;a href="https://nginx.org/en/docs/http/ngx_http_headers_module.html" rel="noopener noreferrer"&gt;Nginx headers module documentation&lt;/a&gt; against your configuration before deciding where to put the directives.&lt;/p&gt;

&lt;p&gt;Apply the change in this order:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Save a copy of the current configuration.&lt;/li&gt;
&lt;li&gt;Add the directives in the block responsible for the page.&lt;/li&gt;
&lt;li&gt;Test the Nginx configuration and resolve any errors.&lt;/li&gt;
&lt;li&gt;Reload Nginx using your deployment’s normal procedure.&lt;/li&gt;
&lt;li&gt;Check the public URL again.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Do not stop at a successful configuration test. The result you need is the intended headers on the live page response.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you add security headers in Apache?
&lt;/h2&gt;

&lt;p&gt;With &lt;code&gt;mod_headers&lt;/code&gt; enabled, add these directives in the applicable virtual host or directory configuration:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight apache"&gt;&lt;code&gt;&lt;span class="nc"&gt;Header&lt;/span&gt; &lt;span class="n"&gt;always&lt;/span&gt; &lt;span class="n"&gt;set&lt;/span&gt; &lt;span class="no"&gt;X&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Content&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Type&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Options&lt;/span&gt; &lt;span class="s2"&gt;"nosniff"&lt;/span&gt;
&lt;span class="nc"&gt;Header&lt;/span&gt; &lt;span class="n"&gt;always&lt;/span&gt; &lt;span class="n"&gt;set&lt;/span&gt; &lt;span class="nc"&gt;Referrer&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Policy&lt;/span&gt; &lt;span class="s2"&gt;"strict-origin-when-cross-origin"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Use this Apache configuration instead of the Nginx example. Choose the configuration that actually serves the affected response.&lt;/p&gt;

&lt;p&gt;Before saving the change, review existing &lt;code&gt;Header&lt;/code&gt; directives and headers returned by an upstream application. Apache maintains separate header tables, so &lt;code&gt;Header always set&lt;/code&gt; does not automatically eliminate every duplicate created elsewhere. The &lt;a href="https://httpd.apache.org/docs/2.4/mod/mod_headers.html" rel="noopener noreferrer"&gt;Apache mod_headers documentation&lt;/a&gt; explains &lt;code&gt;always&lt;/code&gt;, directive scope, and duplicate-header considerations.&lt;/p&gt;

&lt;p&gt;Then:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Save a copy of the current configuration.&lt;/li&gt;
&lt;li&gt;Confirm that &lt;code&gt;mod_headers&lt;/code&gt; is enabled.&lt;/li&gt;
&lt;li&gt;Add the directives in the applicable configuration.&lt;/li&gt;
&lt;li&gt;Test the Apache configuration and fix any errors.&lt;/li&gt;
&lt;li&gt;Reload Apache using your normal deployment procedure.&lt;/li&gt;
&lt;li&gt;Inspect the live page response for the intended names and values.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If a header appears more than once, investigate the existing directives and upstream response before adding more configuration. The goal is an intentional policy, not merely a header name appearing somewhere in the response.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you verify the fix and choose additional headers?
&lt;/h2&gt;

&lt;p&gt;Run the &lt;a href="https://sitecheckly.com/tools/security-headers-checker" rel="noopener noreferrer"&gt;security headers checker&lt;/a&gt; again on the same URL. Follow redirects and confirm that the intended headers appear on the final response.&lt;/p&gt;

&lt;p&gt;Check both the names and values:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="no"&gt;X&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Content&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Type&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Options&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;nosniff&lt;/span&gt;
&lt;span class="nc"&gt;Referrer&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Policy&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;strict&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;origin&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;when&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;cross&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;origin&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A header’s presence alone is not enough. For example, &lt;code&gt;nosniff&lt;/code&gt; still requires you to serve resources with the correct content type, as explained in &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options" rel="noopener noreferrer"&gt;MDN’s X-Content-Type-Options documentation&lt;/a&gt;. Check that the page and its resources still work after deployment.&lt;/p&gt;

&lt;p&gt;Test other important URLs separately. Include pages handled by different applications, server blocks, or proxy paths. Keep a small verification record with the URL, expected headers, and observed result so the scope of the fix is clear.&lt;/p&gt;

&lt;h3&gt;
  
  
  Plan Content Security Policy around the page
&lt;/h3&gt;

&lt;p&gt;Do not treat a generic Content Security Policy as a drop-in fix. Build the policy around the resources the page actually needs. Use the &lt;a href="https://sitecheckly.com/blog/content-security-policy-example-report-only" rel="noopener noreferrer"&gt;CSP report-only guide&lt;/a&gt; to test a proposed policy before enforcing it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Confirm HTTPS before enabling HSTS
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;Strict-Transport-Security&lt;/code&gt; tells browsers to use HTTPS for future requests to the host during the policy’s lifetime. Browsers only accept it over HTTPS. Review &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security" rel="noopener noreferrer"&gt;MDN’s HSTS guide&lt;/a&gt; before choosing a policy, especially one that includes subdomains.&lt;/p&gt;

&lt;p&gt;Confirm that HTTPS works correctly before deployment. The &lt;a href="https://sitecheckly.com/blog/hsts-header-guide" rel="noopener noreferrer"&gt;HSTS setup guide&lt;/a&gt; provides a focused path for that change. Do not add HSTS solely to clear a missing-header warning without checking its scope.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do next&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Fix the flagged page at the layer that controls its response.&lt;/li&gt;
&lt;li&gt;Test and reload the relevant server configuration.&lt;/li&gt;
&lt;li&gt;Verify the public response on the same URL.&lt;/li&gt;
&lt;li&gt;Check other important URLs individually and plan additional policies separately.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does X-Content-Type-Options fix an incorrect Content-Type?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Set the correct Content-Type for each resource; nosniff tells browsers not to reinterpret applicable responses as a different type. See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options" rel="noopener noreferrer"&gt;MDN&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does Referrer-Policy hide every referrer?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Not necessarily. The strict-origin-when-cross-origin policy can send the full referrer for same-origin requests and the origin for eligible cross-origin requests. See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy" rel="noopener noreferrer"&gt;MDN&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a security header be present but ineffective?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes. A header can be present with an invalid or unsuitable value, so check its value and behavior rather than only its presence. Consult the relevant header documentation, such as &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy" rel="noopener noreferrer"&gt;MDN’s Referrer-Policy reference&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>securityheaders</category>
      <category>httpheaders</category>
      <category>nginx</category>
      <category>apache</category>
    </item>
    <item>
      <title>HSTS Header Guide: Settings, Preload and Platform Setup</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Wed, 18 Nov 2026 08:52:53 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/hsts-header-guide-settings-preload-and-platform-setup-4gl</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/hsts-header-guide-settings-preload-and-platform-setup-4gl</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/hsts-header-guide" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The HSTS header tells browsers to use HTTPS for a domain after receiving the header over HTTPS. In the Sitecheckly survey, &lt;a href="https://sitecheckly.com/blog/website-security-statistics-october-2026" rel="noopener noreferrer"&gt;40% of analyzed sites were missing it&lt;/a&gt;. Set &lt;code&gt;Strict-Transport-Security&lt;/code&gt; on HTTPS responses, start with a short &lt;code&gt;max-age&lt;/code&gt;, and add &lt;code&gt;includeSubDomains&lt;/code&gt; or &lt;code&gt;preload&lt;/code&gt; only after checking their risks. &lt;a href="https://datatracker.ietf.org/doc/html/rfc6797" rel="noopener noreferrer"&gt;RFC 6797&lt;/a&gt; defines HSTS.&lt;/p&gt;

&lt;p&gt;The October 2026 Sitecheckly survey covered the Tranco top 10,000, using Tranco list 7462X. The ranking covers 2026-10-02 to 2026-10-31. Home pages were fetched on 2026-11-01, and 4,934 of 10,000 domains could be analyzed. The rest were mostly CDN, DNS and API hosts, sites that ask crawlers to stay away in robots.txt, or sites that blocked automated requests. See the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt; for how Sitecheckly runs its checks.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does the HSTS header do?
&lt;/h2&gt;

&lt;p&gt;HTTP Strict Transport Security, or HSTS, lets a host tell browsers to use HTTPS for future requests. While the policy is active, the browser upgrades HTTP requests before sending them. It also prevents users from clicking through certificate errors for that host.&lt;/p&gt;

&lt;p&gt;A previously received policy cannot protect a browser's first visit. If that first request uses HTTP, the browser has not yet learned the site's policy. Browser preload lists can address that gap. These behaviors are explained in &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security" rel="noopener noreferrer"&gt;MDN's Strict-Transport-Security reference&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Start with this HTTPS response header:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="na"&gt;Strict-Transport-Security: max-age&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;300&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The directives control how long the policy lasts and how broadly it applies:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Directive&lt;/th&gt;
&lt;th&gt;Meaning&lt;/th&gt;
&lt;th&gt;Safe rollout approach&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;max-age=300&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Store the policy for 300 seconds. Receiving the header again refreshes its expiration.&lt;/td&gt;
&lt;td&gt;Use a short policy while testing, then increase it.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;includeSubDomains&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Apply the policy to subdomains as well as the host sending it.&lt;/td&gt;
&lt;td&gt;Add it only after checking every affected subdomain.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;preload&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Signal willingness to be included in browser preload lists. It does not submit the domain by itself.&lt;/td&gt;
&lt;td&gt;Treat it as a separate deployment decision.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Browsers ignore HSTS received over plain HTTP. HTTPS must already work; HSTS does not install a certificate or repair an invalid one. See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security" rel="noopener noreferrer"&gt;MDN's directive and processing guidance&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Preloading requires more than adding a directive. Review HTTPS readiness across subdomains, meet the submission requirements, and submit the domain separately. Removal from browser preload lists can take time. Check the current requirements at &lt;a href="https://hstspreload.org/" rel="noopener noreferrer"&gt;hstspreload.org&lt;/a&gt; before committing.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you add HSTS in Nginx?
&lt;/h2&gt;

&lt;p&gt;Add this directive inside your existing HTTPS &lt;code&gt;server&lt;/code&gt; block:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nginx"&gt;&lt;code&gt;&lt;span class="n"&gt;add_header&lt;/span&gt; &lt;span class="nc"&gt;Strict&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Transport&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Security&lt;/span&gt; &lt;span class="s2"&gt;"max-age=300"&lt;/span&gt; &lt;span class="n"&gt;always&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;always&lt;/code&gt; parameter makes Nginx add the header regardless of the response status. Without it, &lt;code&gt;add_header&lt;/code&gt; applies only to the status codes listed in the module documentation.&lt;/p&gt;

&lt;p&gt;Check nested &lt;code&gt;location&lt;/code&gt; blocks too. Under the default inheritance behavior, a block with its own &lt;code&gt;add_header&lt;/code&gt; directives does not inherit the parent block's headers. A header configured at the server level may therefore be absent from a particular route. See the &lt;a href="https://nginx.org/en/docs/http/ngx_http_headers_module.html#add_header" rel="noopener noreferrer"&gt;Nginx headers module documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;After editing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Test the Nginx configuration with your deployment's configuration-test command.&lt;/li&gt;
&lt;li&gt;Reload Nginx only after the test passes.&lt;/li&gt;
&lt;li&gt;Check a normal page, a redirect, and an error response at the public HTTPS URL.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep HTTP-to-HTTPS redirects in place. Browsers without a stored policy still need a way to reach HTTPS and receive HSTS. The distinction between insecure requests and learned HSTS policies is defined in &lt;a href="https://datatracker.ietf.org/doc/html/rfc6797" rel="noopener noreferrer"&gt;RFC 6797&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you add HSTS in Apache?
&lt;/h2&gt;

&lt;p&gt;With &lt;code&gt;mod_headers&lt;/code&gt; enabled, add this directive inside the existing HTTPS virtual host:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight apache"&gt;&lt;code&gt;&lt;span class="nc"&gt;Header&lt;/span&gt; &lt;span class="n"&gt;always&lt;/span&gt; &lt;span class="n"&gt;set&lt;/span&gt; &lt;span class="nc"&gt;Strict&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Transport&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Security&lt;/span&gt; &lt;span class="s2"&gt;"max-age=300"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Apache's &lt;code&gt;always&lt;/code&gt; condition allows the header to be applied beyond successful responses, including error responses. Apache also maintains separate internal response-header tables, so headers set by an application or another module can require special care. See the &lt;a href="https://httpd.apache.org/docs/2.4/mod/mod_headers.html" rel="noopener noreferrer"&gt;Apache mod_headers documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Test the Apache configuration, then reload the service using your deployment's normal process.&lt;/p&gt;

&lt;p&gt;Inspect the final public response afterward. If both Apache and an upstream application set HSTS, check for duplicate headers. Prefer one configuration owner rather than maintaining competing policies in several places.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you enable HSTS in Cloudflare?
&lt;/h2&gt;

&lt;p&gt;Use Cloudflare's dedicated HSTS setting:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Select the domain in the Cloudflare dashboard.&lt;/li&gt;
&lt;li&gt;Open &lt;strong&gt;SSL/TLS&lt;/strong&gt;, then &lt;strong&gt;Edge Certificates&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Find &lt;strong&gt;HTTP Strict Transport Security (HSTS)&lt;/strong&gt; and enable it.&lt;/li&gt;
&lt;li&gt;Read the warning and choose a short maximum age for the initial rollout.&lt;/li&gt;
&lt;li&gt;Leave &lt;strong&gt;includeSubDomains&lt;/strong&gt; and &lt;strong&gt;preload&lt;/strong&gt; off until you have checked their impact.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Confirm that HTTPS works before enabling the policy. Follow &lt;a href="https://developers.cloudflare.com/ssl/edge-certificates/additional-options/http-strict-transport-security/" rel="noopener noreferrer"&gt;Cloudflare's HSTS setup and requirements&lt;/a&gt; for the available controls and rollback warnings.&lt;/p&gt;

&lt;p&gt;After saving, inspect the public HTTPS response rather than only the origin response. Avoid managing conflicting HSTS values at Cloudflare and your origin. Choose which layer owns the policy and verify what visitors actually receive.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you add HSTS in Next.js?
&lt;/h2&gt;

&lt;p&gt;For a project using CommonJS in &lt;code&gt;next.config.js&lt;/code&gt;, add this header configuration. If the file already contains settings, merge the &lt;code&gt;headers()&lt;/code&gt; function into the existing exported object.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;module&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;exports&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="nf"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
      &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;source&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'/:path*'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="n"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
          &lt;span class="p"&gt;{&lt;/span&gt;
            &lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'Strict-Transport-Security'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
            &lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'max-age=300'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
          &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;headers()&lt;/code&gt; configuration sets response headers for matching paths. The &lt;code&gt;/:path*&lt;/code&gt; pattern matches paths throughout the application. See the &lt;a href="https://nextjs.org/docs/app/api-reference/config/next-config-js/headers" rel="noopener noreferrer"&gt;Next.js headers configuration reference&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Deploy the change and check the public HTTPS response. Do not stop at checking a local development server.&lt;/p&gt;

&lt;p&gt;If your hosting platform or reverse proxy already manages HSTS, choose one layer to own it. Keep this application-level configuration only if it is the intended source of the public policy.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you add HSTS in Express?
&lt;/h2&gt;

&lt;p&gt;Register middleware before the routes that should receive the header. Add this after creating your Express &lt;code&gt;app&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="n"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;use&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;req&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;res&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;next&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;set&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'Strict-Transport-Security'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;'max-age=300'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nf"&gt;next&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;res.set()&lt;/code&gt; method sets the response header, and &lt;code&gt;next()&lt;/code&gt; passes control to the following middleware or route. The header-setting method is defined in the &lt;a href="https://github.com/expressjs/express/blob/master/lib/response.js" rel="noopener noreferrer"&gt;Express response implementation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Serve the application over HTTPS or terminate HTTPS at a trusted proxy. This middleware sets a header; it is not a TLS configuration.&lt;/p&gt;

&lt;p&gt;Verify the public HTTPS response after deployment. If the proxy also sets HSTS, remove the duplicate configuration or make the proxy the sole policy owner.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you check HSTS and decide whether to preload?
&lt;/h2&gt;

&lt;p&gt;Check the public HTTPS URL with Sitecheckly's free &lt;a href="https://sitecheckly.com/tools/security-headers-checker" rel="noopener noreferrer"&gt;security headers checker&lt;/a&gt;. For a broader passive check, run the separate &lt;a href="https://sitecheckly.com/security-audit" rel="noopener noreferrer"&gt;security audit&lt;/a&gt;. It is free, requires no sign-up, and audits the entered page, not the whole site.&lt;/p&gt;

&lt;p&gt;You can also inspect the response from a terminal:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -I https://example.com/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Look for the deployed policy:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="na"&gt;Strict-Transport-Security: max-age&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;300&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Check redirect responses and their destinations separately. Test representative subdomains too, especially before broadening the policy.&lt;/p&gt;

&lt;h3&gt;
  
  
  Increase max-age after the trial
&lt;/h3&gt;

&lt;p&gt;A short &lt;code&gt;max-age&lt;/code&gt; is a rollout step, not necessarily the intended permanent setting. In the survey, &lt;a href="https://sitecheckly.com/blog/website-security-statistics-october-2026" rel="noopener noreferrer"&gt;11% of analyzed sites were flagged for a short HSTS max-age&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Once HTTPS and header delivery are working as intended, increase the policy duration deliberately. Do not copy a long-lived policy into production before checking certificate renewal, redirects, and the subdomains you plan to cover.&lt;/p&gt;

&lt;h3&gt;
  
  
  Treat includeSubDomains and preload as separate decisions
&lt;/h3&gt;

&lt;p&gt;Before adding &lt;code&gt;includeSubDomains&lt;/code&gt;, inventory affected subdomains, including services operated by third parties. Confirm that each can remain available over HTTPS.&lt;/p&gt;

&lt;p&gt;Before adding &lt;code&gt;preload&lt;/code&gt;, review the current &lt;a href="https://hstspreload.org/" rel="noopener noreferrer"&gt;preload submission and removal guidance&lt;/a&gt;. Adding the directive alone does not enroll the domain, and removing the header is not an immediate way out of a browser preload list.&lt;/p&gt;

&lt;h3&gt;
  
  
  What to do next
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Pick one layer to manage HSTS.&lt;/li&gt;
&lt;li&gt;Deploy a short policy and inspect the public HTTPS response.&lt;/li&gt;
&lt;li&gt;Test before increasing its duration or scope.&lt;/li&gt;
&lt;li&gt;Review the &lt;a href="https://sitecheckly.com/blog/security-headers-list-recommended-values" rel="noopener noreferrer"&gt;security headers list and recommended values&lt;/a&gt; to check the other headers your page needs.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Can I disable an HSTS policy?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Send Strict-Transport-Security: max-age=0 over HTTPS to tell browsers that receive it to remove the stored policy. Preloaded entries require a separate removal process. See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security" rel="noopener noreferrer"&gt;MDN&lt;/a&gt; and &lt;a href="https://hstspreload.org/" rel="noopener noreferrer"&gt;hstspreload.org&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does HSTS install an SSL certificate?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. HSTS is a browser policy, not a certificate. HTTPS must already work for the host; see &lt;a href="https://datatracker.ietf.org/doc/html/rfc6797" rel="noopener noreferrer"&gt;RFC 6797&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do browsers accept HSTS over HTTP?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Browsers ignore an HSTS header received over insecure HTTP; the policy must be sent over HTTPS. See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security" rel="noopener noreferrer"&gt;MDN&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>hsts</category>
      <category>securityheaders</category>
      <category>https</category>
      <category>websecurity</category>
    </item>
    <item>
      <title>Answer First Content: How to Structure a Page for AI Search</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Wed, 18 Nov 2026 08:52:49 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/answer-first-content-how-to-structure-a-page-for-ai-search-4ggg</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/answer-first-content-how-to-structure-a-page-for-ai-search-4ggg</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/answer-first-content-ai-search" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Answer-first content puts a concise, self-contained answer immediately after the question it addresses. Follow it with the details, evidence and exceptions readers need. Use descriptive question headings, lists or tables where they make information easier to understand, and identify the author and meaningful update dates. This structure helps readers find answers, but does not guarantee an AI engine will cite the page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why use answer-first content?
&lt;/h2&gt;

&lt;p&gt;In the survey, &lt;strong&gt;70%&lt;/strong&gt; of the sites we analyzed had no concise answer-first paragraphs detected. That is a finding about page structure, not proof that those pages were unhelpful or excluded from AI search. See the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;Sitecheckly survey methodology&lt;/a&gt; for the audit context.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Survey method:&lt;/strong&gt; The October 2026 Sitecheckly survey examined the Tranco top 10,000 using Tranco list 7462X. The ranking covers 2026-10-02 to 2026-10-31. Home pages were fetched on 2026-11-01. Of 10,000 domains, 4,934 could be analyzed. The rest were mostly CDN, DNS and API hosts, sites that ask crawlers to stay away in robots.txt, or sites that blocked automated requests. These findings describe the home pages analyzed, not every page on those domains.&lt;/p&gt;

&lt;p&gt;The practical reason to use answer first content is simple: readers should not have to work through background material before finding the answer they came for. Put the useful response where they expect it, then give them enough detail to understand and apply it.&lt;/p&gt;

&lt;p&gt;Treat AI search content structure as an editorial choice, not a citation trick. Google says that meeting its requirements and following its guidance does not guarantee inclusion in its AI features. Its &lt;a href="https://developers.google.com/search/docs/appearance/ai-features" rel="noopener noreferrer"&gt;guidance for AI features and websites&lt;/a&gt; also points back to established SEO practices rather than special AI-only formatting.&lt;/p&gt;

&lt;p&gt;If you need the broader context, read the &lt;a href="https://sitecheckly.com/blog/what-is-answer-engine-optimization" rel="noopener noreferrer"&gt;introduction to answer engine optimization&lt;/a&gt;. Here, the task is narrower: make the answer on a specific page easier to find and understand.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you write a direct answer?
&lt;/h2&gt;

&lt;p&gt;Draft a &lt;strong&gt;40–60 word answer immediately below the main question&lt;/strong&gt;. State the answer before the background. Name the subject, give the useful response, and include any qualification that would materially change what the reader should do.&lt;/p&gt;

&lt;p&gt;That word range is an editorial guideline, not a search engine requirement. Do not pad a simple answer or cut an essential warning just to fit it.&lt;/p&gt;

&lt;p&gt;Use this editing sequence:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Identify the reader's question.&lt;/strong&gt; Write down what someone should know or be able to do after reading the section.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Answer it in the opening sentence.&lt;/strong&gt; Remove lead-ins such as “There are many factors to consider.”&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Make the paragraph stand alone.&lt;/strong&gt; Replace unclear references such as “this approach” with the thing you mean.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep essential limits close.&lt;/strong&gt; If the answer applies only under certain conditions, say so before the reader acts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add support afterward.&lt;/strong&gt; Follow with evidence, examples, exceptions and practical steps.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example, consider a section answering “How should you write a page title?”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;There are many things to consider when choosing a page title. First, think about your audience.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Write a page title that accurately describes the page and uses the terms your audience would expect. Keep it distinct from titles on other pages, then check how it appears in search results.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The rewrite gives the reader something to do. The original delays the advice. Use the rewrite as a model for directness, rather than as a word-count template.&lt;/p&gt;

&lt;p&gt;You do not need to remove all introductory context. Move it below the answer when it is still useful. If a term needs explaining before the answer makes sense, define it briefly rather than adding a long preamble.&lt;/p&gt;

&lt;h2&gt;
  
  
  How should question headings, lists and tables support the answer?
&lt;/h2&gt;

&lt;p&gt;Use a question heading when it matches a real reader question. Answer it directly beneath the heading. Use a descriptive heading when it communicates the section's purpose more naturally.&lt;/p&gt;

&lt;p&gt;For example, “How do you cancel a subscription?” sets a clear expectation. “Subscription information” is broader and may be less useful if cancellation is the section's actual subject. But a heading such as “Cancellation fees” can be perfectly clear without becoming a question.&lt;/p&gt;

&lt;p&gt;Google's &lt;a href="https://developers.google.com/search/docs/fundamentals/creating-helpful-content" rel="noopener noreferrer"&gt;people-first content guidance&lt;/a&gt; encourages descriptive headings and content that helps people achieve their goals. Use that as the standard, rather than trying to make every heading look alike.&lt;/p&gt;

&lt;p&gt;In the survey, &lt;strong&gt;68%&lt;/strong&gt; of the sites we analyzed had no question-style subheadings, and &lt;strong&gt;21%&lt;/strong&gt; had no lists or tables. These &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;structural findings&lt;/a&gt; are prompts for review, not requirements to add a particular format everywhere.&lt;/p&gt;

&lt;p&gt;Choose the format that suits the information:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Reader's task&lt;/th&gt;
&lt;th&gt;Useful format&lt;/th&gt;
&lt;th&gt;What to avoid&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Follow a procedure&lt;/td&gt;
&lt;td&gt;An ordered list of actions&lt;/td&gt;
&lt;td&gt;Hiding the sequence in a long paragraph&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Review distinct requirements&lt;/td&gt;
&lt;td&gt;A bulleted checklist&lt;/td&gt;
&lt;td&gt;Mixing unrelated advice into each item&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Compare alternatives&lt;/td&gt;
&lt;td&gt;A table with consistent fields&lt;/td&gt;
&lt;td&gt;Comparing different attributes in every row&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Understand a definition or explanation&lt;/td&gt;
&lt;td&gt;A concise paragraph&lt;/td&gt;
&lt;td&gt;Forcing a simple answer into a table&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Keep each section focused. If a heading asks about price, answer the price question before moving into setup or support. If those topics need substantial explanation, give them their own descriptive headings.&lt;/p&gt;

&lt;p&gt;A useful editing test is to read only the headings and the first paragraph beneath each. Ask whether that skim gives a reader a coherent, accurate outline of the page. Then check that the supporting detail adds substance rather than repeating the opening answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Should you add an author and update date?
&lt;/h2&gt;

&lt;p&gt;Identify the author where readers would reasonably expect to know who created the content. Give relevant context, not just a name. Explain the author's practical experience, research process or role when that helps readers assess the answer.&lt;/p&gt;

&lt;p&gt;Useful context might describe:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Whether the author used the product or carried out the process.&lt;/li&gt;
&lt;li&gt;Which primary documents informed the explanation.&lt;/li&gt;
&lt;li&gt;Whether a qualified reviewer checked specialist advice.&lt;/li&gt;
&lt;li&gt;What limitations apply to the author's testing or research.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Only include experience and review claims you can substantiate. A detailed biography is not necessary for every page, and a product page may need different attribution from a technical tutorial.&lt;/p&gt;

&lt;p&gt;Show an update date when the page has been substantially revised. Do not change dates merely to make unchanged content appear fresh. Google's &lt;a href="https://developers.google.com/search/docs/fundamentals/creating-helpful-content" rel="noopener noreferrer"&gt;guidance on authorship and content freshness&lt;/a&gt; specifically addresses both clear authorship and date changes made only to suggest freshness.&lt;/p&gt;

&lt;p&gt;When useful, add a short update note explaining what changed. “Revised the setup instructions after testing the current workflow” tells readers more than a new date alone, provided that is what actually happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  How can you check and improve your page?
&lt;/h2&gt;

&lt;p&gt;Enter the page URL in the free &lt;a href="https://sitecheckly.com/aeo-audit" rel="noopener noreferrer"&gt;Sitecheckly AEO audit&lt;/a&gt;. It checks the entered page, not the whole site, and requires no sign-up.&lt;/p&gt;

&lt;p&gt;Use the results alongside a manual review. A missing format is not automatically a content problem. A page may have no comparison table because there is nothing useful to compare.&lt;/p&gt;

&lt;p&gt;Review the page with these questions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Direct answer:&lt;/strong&gt; Does the opening answer address the main question without making readers search for it?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Self-contained wording:&lt;/strong&gt; Can someone understand the answer without reading the preceding section?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Headings:&lt;/strong&gt; Do they describe the content beneath them? Where a heading asks a question, does the next paragraph answer it?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Supporting structure:&lt;/strong&gt; Would a list clarify the steps, or a table make a comparison easier?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Evidence and exceptions:&lt;/strong&gt; Are supported claims linked to evidence, with important limitations close to the answer?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Authorship and dates:&lt;/strong&gt; Can readers assess who created the content and whether a displayed update reflects a meaningful revision?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Also check that the intended search crawler can access the page. Search and training crawlers are not interchangeable. OpenAI identifies &lt;strong&gt;OAI-SearchBot&lt;/strong&gt; as its search crawler and &lt;strong&gt;GPTBot&lt;/strong&gt; as a crawler for model training in its &lt;a href="https://platform.openai.com/docs/bots" rel="noopener noreferrer"&gt;crawler documentation&lt;/a&gt;. Do not assume a rule for one controls the other. The &lt;a href="https://sitecheckly.com/blog/ai-crawlers-list-user-agents" rel="noopener noreferrer"&gt;AI crawlers guide&lt;/a&gt; explains the distinction across services.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do next&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Choose a page with a clear reader question.&lt;/li&gt;
&lt;li&gt;Rewrite its opening answer and move supporting context below it.&lt;/li&gt;
&lt;li&gt;Fix the structural gaps that matter to that page, then run the audit again.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does answer-first writing mean removing the introduction?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Put the useful answer first, then use the introduction or following paragraphs to add context.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a product page use answer-first writing?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes. Answer the buyer's main question near the relevant product details, then provide specifications, limitations and other supporting information.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Should every heading be a question?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Use question headings where they match reader needs; a clear descriptive heading can be better elsewhere.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does a short answer need sources?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Link to evidence for claims that need support. The supporting detail can follow the concise answer.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>aeo</category>
      <category>contentstructure</category>
      <category>aisearch</category>
      <category>writing</category>
    </item>
    <item>
      <title>JSON-LD Structured Data: Five Types to Add First</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Mon, 16 Nov 2026 08:19:00 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/json-ld-structured-data-five-types-to-add-first-1dja</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/json-ld-structured-data-five-types-to-add-first-1dja</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/json-ld-structured-data-five-types" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Start with Organization and WebSite markup for your business and site, then add Article, FAQPage, and BreadcrumbList where the page content supports them. These types describe entities and page content, but they do not guarantee rich results or AI citations. In the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;Sitecheckly survey&lt;/a&gt;, 51% of analyzed sites had no Schema.org structured data.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is JSON-LD structured data?
&lt;/h2&gt;

&lt;p&gt;JSON-LD is a format for expressing structured data inside a script element. It gives search engines a machine-readable description of the content on a page. Google can use supported structured data to understand that content and make eligible pages available for certain search features, as explained in its &lt;a href="https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data" rel="noopener noreferrer"&gt;introduction to structured data&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The survey figures come from the October 2026 Sitecheckly survey of the Tranco top 10,000 (Tranco list 7462X). The ranking covers 2026-10-02 to 2026-10-31. The home pages were fetched on 2026-11-01. Of those domains, 4,934 of 10,000 could be analyzed. The rest were mostly CDN, DNS and API hosts, sites that ask crawlers to stay away in robots.txt, or sites that blocked automated requests. See the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;survey methodology&lt;/a&gt; for the scope and limitations.&lt;/p&gt;

&lt;p&gt;Treat structured data for SEO as a description, not a promise of visibility. Adding markup does not guarantee an AI answer citation either. For the broader context, read &lt;a href="https://sitecheckly.com/blog/what-is-answer-engine-optimization" rel="noopener noreferrer"&gt;what answer engine optimization means&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The practical starting point is simple: choose a type that matches the page, replace every example value, and check the published result. Do not add all five types to every URL.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which JSON-LD types describe your organization and website?
&lt;/h2&gt;

&lt;p&gt;Organization and WebSite answer different questions: who is behind the site, and what is the site called?&lt;/p&gt;

&lt;h3&gt;
  
  
  Organization: identify the organization
&lt;/h3&gt;

&lt;p&gt;Google says &lt;a href="https://developers.google.com/search/docs/appearance/structured-data/organization" rel="noopener noreferrer"&gt;Organization structured data&lt;/a&gt; can help it understand and disambiguate an organization. Use details that match the organization represented on your site.&lt;/p&gt;

&lt;p&gt;This minimal example identifies an organization by its name and URL:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;script&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"application/ld+json"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="s2"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Organization"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Example Company"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/"&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replace &lt;code&gt;Example Company&lt;/code&gt; with your actual organization name and &lt;code&gt;https://example.com/&lt;/code&gt; with its real home page URL. Do not publish the placeholder values.&lt;/p&gt;

&lt;p&gt;Start with information you can verify. If you add more properties, use the Organization documentation to check their meaning rather than guessing from their names.&lt;/p&gt;

&lt;h3&gt;
  
  
  WebSite: describe the site itself
&lt;/h3&gt;

&lt;p&gt;Use WebSite markup on the home page. Google uses it as a signal for the site name shown in search, but it does not guarantee that your preferred name will appear. Follow Google's &lt;a href="https://developers.google.com/search/docs/appearance/site-names" rel="noopener noreferrer"&gt;site name guidance&lt;/a&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;script&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"application/ld+json"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="s2"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"WebSite"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Example Company"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/"&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;These examples look similar because both include a name and URL. Their types give those values different meanings. Organization describes the organization; WebSite describes the website.&lt;/p&gt;

&lt;p&gt;Use the actual site name for WebSite. Do not turn the name field into a list of search keywords.&lt;/p&gt;

&lt;h2&gt;
  
  
  When should you add Article and FAQPage markup?
&lt;/h2&gt;

&lt;p&gt;Add these types only when the page contains the content they describe. The following JSON-LD examples are minimal starting points, not complete content models or guaranteed rich-result recipes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Article: describe an actual article
&lt;/h3&gt;

&lt;p&gt;Use Article for a page that is an article. Google says &lt;a href="https://developers.google.com/search/docs/appearance/structured-data/article" rel="noopener noreferrer"&gt;Article structured data&lt;/a&gt; can help it understand the page and display better title text, images, and date information.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;script&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"application/ld+json"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="s2"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Article"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"headline"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Example article"&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replace the headline with the article's actual headline. Then review the relevant recommended properties in Google's documentation. Add details such as author, images, and publication or modification dates when they are available and accurate.&lt;/p&gt;

&lt;p&gt;Do not invent a publication date to fill a field. Do not use Article merely because a product page or contact page contains a few paragraphs of text.&lt;/p&gt;

&lt;p&gt;The snippet above demonstrates the type and headline. It is not a substitute for reviewing the full Article guidance before publishing.&lt;/p&gt;

&lt;h3&gt;
  
  
  FAQPage: describe visible questions and answers
&lt;/h3&gt;

&lt;p&gt;Use FAQPage only when the questions and answers are visible on the page. Google has deprecated FAQ rich results, so do not add FAQPage markup expecting that search feature. See Google's &lt;a href="https://developers.google.com/search/updates" rel="noopener noreferrer"&gt;documentation updates&lt;/a&gt; for the deprecation notice.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;script&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"application/ld+json"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="s2"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"FAQPage"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"mainEntity"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Question"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"What is the return policy?"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"acceptedAnswer"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Answer"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"text"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Returns are accepted within the stated return period."&lt;/span&gt;
      &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replace both the question and answer with the page's actual content. The example answer is deliberately generic; it is not a return policy you should copy into a live store.&lt;/p&gt;

&lt;p&gt;Before adding FAQPage, ask whether it describes useful content already present on the page. Do not create hidden questions just to populate the markup.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does BreadcrumbList describe a page's location?
&lt;/h2&gt;

&lt;p&gt;Use BreadcrumbList when the page has a corresponding breadcrumb trail. Google uses &lt;a href="https://developers.google.com/search/docs/appearance/structured-data/breadcrumb" rel="noopener noreferrer"&gt;breadcrumb structured data&lt;/a&gt; to categorize page information in search results.&lt;/p&gt;

&lt;p&gt;This example represents a trail from Home to Articles:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;script&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"application/ld+json"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="s2"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"BreadcrumbList"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"itemListElement"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"ListItem"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"position"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Home"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"item"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/"&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"ListItem"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"position"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Articles"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"item"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/articles/"&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replace the names and URLs with the real navigation path. Keep the order consistent with the breadcrumb trail shown on the page.&lt;/p&gt;

&lt;p&gt;Do not paste this unchanged onto an individual article if its visible trail includes another step. Describe the page's actual location, rather than reusing the same example everywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you check JSON-LD after adding it?
&lt;/h2&gt;

&lt;p&gt;Check syntax, content accuracy, and search-feature eligibility separately. A minimal Schema.org example is not necessarily eligible for a Google feature.&lt;/p&gt;

&lt;p&gt;Use this workflow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Create a starting snippet.&lt;/strong&gt; Use the free &lt;a href="https://sitecheckly.com/tools/schema-markup-generator" rel="noopener noreferrer"&gt;schema markup generator&lt;/a&gt;, then replace the example values with information from your page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check the markup.&lt;/strong&gt; Use the free &lt;a href="https://sitecheckly.com/tools/schema-markup-validator" rel="noopener noreferrer"&gt;schema markup validator&lt;/a&gt; to check your JSON-LD. Fix reported errors before treating the implementation as finished.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compare it with the page.&lt;/strong&gt; Read each name, headline, question, answer, and URL against the published content. A tool cannot make placeholder text accurate for your business.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Audit the changed URL.&lt;/strong&gt; Run Sitecheckly's free &lt;a href="https://sitecheckly.com/" rel="noopener noreferrer"&gt;SEO and AEO audit&lt;/a&gt; on that page. It checks one page per run and requires no sign-up.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check Google's requirements.&lt;/strong&gt; Use Google's Rich Results Test for supported rich-result eligibility, then review the relevant feature documentation for required properties and content rules. Google's &lt;a href="https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data" rel="noopener noreferrer"&gt;structured data introduction&lt;/a&gt; explains testing and why correct markup does not guarantee display.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Keep those checks distinct. Fixing a syntax error does not prove that a page meets a feature's content requirements. Meeting the requirements does not guarantee that Google will show the feature.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do next&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Choose one page and the types that genuinely describe it.&lt;/li&gt;
&lt;li&gt;Replace every placeholder in the relevant snippets.&lt;/li&gt;
&lt;li&gt;Publish, validate, and check the exact URL you changed.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Do I need to add all five types to every page?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Choose types that describe the page and its actual content. For example, an article type is not appropriate for a page that is not an article.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a page contain more than one JSON-LD type?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes. A page can describe multiple relevant entities, such as an article and its breadcrumb trail. Each description should match the page.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does valid JSON-LD guarantee a rich result?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Valid syntax does not guarantee that a page meets a search feature's requirements or that the feature will appear.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will structured data guarantee a citation in an AI answer?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Structured data can describe content, but adding it does not guarantee an AI answer citation.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>jsonld</category>
      <category>structureddata</category>
      <category>schemamarkup</category>
      <category>seo</category>
    </item>
    <item>
      <title>CVE-2026-119977 WordPress Flaw: Check and Fix Your Site</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Thu, 12 Nov 2026 08:40:16 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/cve-2026-119977-wordpress-flaw-check-and-fix-your-site-587p</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/cve-2026-119977-wordpress-flaw-check-and-fix-your-site-587p</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/cve-2026-119977-wordpress" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;CVE-2026-119977 is a WordPress core race condition that can allow unauthenticated attackers to execute code on the server during a full-package upgrade. &lt;a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog" rel="noopener noreferrer"&gt;CISA reports evidence of exploitation in the wild&lt;/a&gt;. WordPress was detected on &lt;a href="https://sitecheckly.com/tech/wordpress" rel="noopener noreferrer"&gt;12% of the sites analyzed in Sitecheckly’s survey&lt;/a&gt;, but that figure does not measure exposure to this flaw. Check your installed core version, then consult the &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2026-119977" rel="noopener noreferrer"&gt;NVD vulnerability record&lt;/a&gt; for affected versions and the &lt;a href="https://wordpress.org/news/2026/10/wordpress-7-1-4" rel="noopener noreferrer"&gt;WordPress vendor advisory&lt;/a&gt; for the fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is CVE-2026-119977, and which WordPress versions are affected?
&lt;/h2&gt;

&lt;p&gt;The CVE-2026-119977 WordPress flaw is a time-of-check time-of-use, or TOCTOU, race condition. In plain terms, a security-sensitive check and the operation that follows it do not happen as one indivisible action. The gap between them can create an opportunity for an attacker.&lt;/p&gt;

&lt;p&gt;For this vulnerability, the reported problem involves predictable, web-accessible staging paths used during full-package WordPress core upgrades. During that upgrade window, an unauthenticated attacker could execute code on the server. The &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2026-119977" rel="noopener noreferrer"&gt;NVD entry for CVE-2026-119977&lt;/a&gt; provides the vulnerability record and references.&lt;/p&gt;

&lt;p&gt;The upgrade window is an important part of the description. This is not a claim that every WordPress page request exposes the flaw, nor does detecting WordPress establish that an installation is affected.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;For the affected version range, see the NVD vulnerability record linked above.&lt;/strong&gt; Do not infer the range from the advisory’s URL, from a version seen on another site, or from a general list of WordPress vulnerabilities. Use NVD’s explicit affected-version guidance and the vendor’s remediation guidance.&lt;/p&gt;

&lt;p&gt;Keep these questions separate:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Is WordPress installed?&lt;/strong&gt; Technology detection can help answer this.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is the installed core version affected?&lt;/strong&gt; Compare the installed version with the NVD vulnerability record.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Was the installation compromised?&lt;/strong&gt; That requires investigation, not just a version comparison.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why does the CISA KEV listing matter?
&lt;/h2&gt;

&lt;p&gt;CISA added this flaw to its Known Exploited Vulnerabilities catalog on &lt;strong&gt;2026-11-03&lt;/strong&gt;. A KEV listing means there is evidence of exploitation in the wild. It makes this a WordPress exploited vulnerability that warrants prompt attention, rather than only a theoretical concern.&lt;/p&gt;

&lt;p&gt;CISA set &lt;strong&gt;2026-11-06&lt;/strong&gt; as the action deadline for US federal agencies. That deadline is not a universal legal requirement for every WordPress owner. Both the exploitation status and the federal deadline are recorded in the &lt;a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog" rel="noopener noreferrer"&gt;CISA KEV catalog&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For a site owner, the practical response is to establish the installed version and follow the vendor’s instructions promptly. Do not wait for a public-facing scanner to report a problem before checking your installation.&lt;/p&gt;

&lt;p&gt;A KEV listing does &lt;strong&gt;not&lt;/strong&gt; mean your particular site was compromised. It also does not establish that every installation of the named product is vulnerable. Treat it as a reason to prioritize verification and remediation, not as a diagnosis of your server.&lt;/p&gt;

&lt;p&gt;For related entries, see Sitecheckly’s list of &lt;a href="https://sitecheckly.com/tech/wordpress/vulnerabilities" rel="noopener noreferrer"&gt;WordPress vulnerabilities exploited in the wild&lt;/a&gt;. Keep the guidance for this specific CVE separate from instructions for other WordPress flaws.&lt;/p&gt;

&lt;h2&gt;
  
  
  How widespread is WordPress in the survey?
&lt;/h2&gt;

&lt;p&gt;The October 2026 Sitecheckly survey used the Tranco top 10,000, list 7462X. The ranking covered &lt;strong&gt;2026-10-02 to 2026-10-31&lt;/strong&gt;, and home pages were fetched on &lt;strong&gt;2026-11-01&lt;/strong&gt;. Of &lt;strong&gt;10,000&lt;/strong&gt; domains, &lt;strong&gt;4,934&lt;/strong&gt; could be analyzed.&lt;/p&gt;

&lt;p&gt;The remaining domains were mostly CDN, DNS and API hosts, sites asking crawlers to stay away in robots.txt, or sites blocking automated requests. The &lt;a href="https://sitecheckly.com/tech/wordpress" rel="noopener noreferrer"&gt;WordPress usage page&lt;/a&gt; provides the survey’s detection figure and sample context.&lt;/p&gt;

&lt;p&gt;The percentage in the opening describes &lt;strong&gt;detected WordPress use&lt;/strong&gt;, not the share affected by CVE-2026-119977. It does not show how many installations were vulnerable, how many underwent a relevant upgrade, or how many were compromised.&lt;/p&gt;

&lt;p&gt;Do not use the survey’s version-exposure figures to estimate exposure to this flaw. A technology survey and an installation-specific vulnerability check answer different questions. Your next step is to check your own installed core version, not to apply the survey percentage to your site.&lt;/p&gt;

&lt;h2&gt;
  
  
  How can you check your WordPress version?
&lt;/h2&gt;

&lt;p&gt;Start with access you control. Check the WordPress admin panel for the installed core version and record it before comparing it with the NVD vulnerability record.&lt;/p&gt;

&lt;p&gt;If you cannot access the admin panel, inspect the page source or server response headers for version information. Treat these as possible clues, not a guaranteed inventory. &lt;strong&gt;An absent public version does not mean the site is safe.&lt;/strong&gt; A public-facing lookup may identify WordPress without revealing its version.&lt;/p&gt;

&lt;p&gt;Use this workflow:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Check the installation directly.&lt;/strong&gt; Record the core version shown in the admin panel. If someone else manages updates, ask them to confirm the installed version.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check the entered URL externally.&lt;/strong&gt; The free &lt;a href="https://sitecheckly.com/tech-stack" rel="noopener noreferrer"&gt;Sitecheckly tech stack lookup&lt;/a&gt; can help identify publicly visible technology information. It requires no sign-up.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run a separate passive check.&lt;/strong&gt; The &lt;a href="https://sitecheckly.com/security-audit" rel="noopener noreferrer"&gt;Sitecheckly security audit&lt;/a&gt; is free with no sign-up. It checks one page per run, using the URL you enter, and its security checks are passive.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compare with the advisory.&lt;/strong&gt; Use the installed core version and NVD’s affected range to decide whether the installation needs the vendor’s specified fix or mitigation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Do not treat either lookup as proof that the whole installation is unaffected. A passive page check is not an exploitation test and cannot establish that a server was never compromised.&lt;/p&gt;

&lt;p&gt;If the public checks do not reveal a version, keep the status as &lt;strong&gt;unconfirmed&lt;/strong&gt; until you can inspect the installation or obtain confirmation from its administrator. Do not turn missing information into a clean bill of health.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you fix WordPress and respond to a possible compromise?
&lt;/h2&gt;

&lt;p&gt;For this WordPress upgrade vulnerability, follow the &lt;a href="https://wordpress.org/news/2026/10/wordpress-7-1-4" rel="noopener noreferrer"&gt;vendor advisory’s fixed-release or mitigation instructions&lt;/a&gt;. Use the release and procedure the vendor specifies. Do not guess a fixed version or substitute an unrelated configuration change.&lt;/p&gt;

&lt;p&gt;After applying the instructions, check the installed core version again and record what changed. If a hosting provider or developer performs the work, ask for confirmation of the resulting version and the actions taken.&lt;/p&gt;

&lt;h3&gt;
  
  
  If compromise is possible
&lt;/h3&gt;

&lt;p&gt;Treat remediation and investigation as separate tasks. Applying a fix addresses the vulnerability; it does not, by itself, establish what happened before the fix.&lt;/p&gt;

&lt;p&gt;Follow the vendor’s response guidance. Rotate credentials and review relevant server and application logs as part of the response. Use &lt;a href="https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk" rel="noopener noreferrer"&gt;CISA’s forensics triage guidance&lt;/a&gt; as a reference when planning that review.&lt;/p&gt;

&lt;p&gt;Use the findings to decide whether further incident-response assistance is needed. If you cannot confidently assess the evidence, involve the person or provider responsible for the server rather than relying on a passive audit result.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do next&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Confirm and record your installed WordPress core version.&lt;/li&gt;
&lt;li&gt;Compare it with NVD’s affected-version guidance and apply the vendor’s specified fix or mitigation.&lt;/li&gt;
&lt;li&gt;If compromise is possible, complete the credential and log review, then decide whether specialist assistance is needed.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does a KEV listing mean my WordPress site was compromised?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. The listing means exploitation has been observed in the wild, not that every installation was hit. Check your version and investigate signs of compromise.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does the federal deadline apply to every WordPress site?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;CISA set the stated deadline for US federal agencies. Site owners should still treat evidence of active exploitation as a reason to act promptly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a passive security audit prove that my site was not compromised?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. A passive audit checks externally observable information; it cannot replace a review of server and application logs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does the survey show how many sites were affected by this CVE?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. WordPress detection alone does not establish an affected version or show whether a site was compromised.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>vulnerability</category>
      <category>cisakev</category>
      <category>sitesecurity</category>
    </item>
    <item>
      <title>Vibe Coding Security Statistics: AI App Survey</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Tue, 10 Nov 2026 12:34:35 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/vibe-coding-security-statistics-ai-app-survey-2lc1</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/vibe-coding-security-statistics-ai-app-survey-2lc1</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/ai-built-app-security-statistics-november-2026" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;In the survey, 92% of AI-built apps were missing Content-Security-Policy, 89% lacked clickjacking protection, and 55% loaded Supabase directly from the browser. Browser access to Supabase is not itself a vulnerability. These &lt;a href="https://sitecheckly.com/data/ai-built-apps" rel="noopener noreferrer"&gt;vibe coding security statistics&lt;/a&gt; point to header configuration gaps and a need to verify database permissions, protect secret keys, and keep sensitive instructions out of client code.&lt;/p&gt;

&lt;p&gt;The sample covered 560 public apps that their makers listed on Made with Lovable, a showcase of apps built with Lovable. Of those, 474 served a page that could be analyzed. Because makers chose to list their apps, the sample leans toward launched projects. It does not represent every AI-built app or every Lovable project.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do AI-built apps compare with top websites?
&lt;/h2&gt;

&lt;p&gt;The average security score in the survey was 76.3 out of 100, compared with 77.1 for the Tranco top-sites survey. Those similar averages hide differences in individual checks.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Observable finding&lt;/th&gt;
&lt;th&gt;AI-built apps&lt;/th&gt;
&lt;th&gt;Top sites&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Missing Cross-Origin-Opener-Policy (COOP)&lt;/td&gt;
&lt;td&gt;98%&lt;/td&gt;
&lt;td&gt;95%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Missing Content-Security-Policy (CSP)&lt;/td&gt;
&lt;td&gt;92%&lt;/td&gt;
&lt;td&gt;66%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No clickjacking protection&lt;/td&gt;
&lt;td&gt;89%&lt;/td&gt;
&lt;td&gt;43%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cookies without a SameSite attribute&lt;/td&gt;
&lt;td&gt;71%&lt;/td&gt;
&lt;td&gt;38%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No CAA records&lt;/td&gt;
&lt;td&gt;95%&lt;/td&gt;
&lt;td&gt;78%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No DMARC record&lt;/td&gt;
&lt;td&gt;72%&lt;/td&gt;
&lt;td&gt;24%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No SPF record&lt;/td&gt;
&lt;td&gt;69%&lt;/td&gt;
&lt;td&gt;19%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Third-party scripts without Subresource Integrity&lt;/td&gt;
&lt;td&gt;30%&lt;/td&gt;
&lt;td&gt;61%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are different kinds of findings. CAA, SPF, and DMARC all use DNS records, not HTTP response headers. CAA restricts certificate issuance, while SPF and DMARC concern email. They should not be treated as interchangeable with CSP or cookie settings. The dataset separates these observable checks; a missing control is not, by itself, proof of an exploitable app.&lt;/p&gt;

&lt;p&gt;The comparison also runs in both directions. Third-party scripts without Subresource Integrity appeared less often in the AI-built apps than in the top-sites survey. That does not cancel out other gaps, just as missing COOP does not carry the same implications as a leaked secret key.&lt;/p&gt;

&lt;p&gt;Use the findings as a configuration checklist:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Configure CSP for the resources your app needs.&lt;/strong&gt; A policy copied from another project may not fit your scripts, styles, connections, or embedded content. The &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP" rel="noopener noreferrer"&gt;MDN CSP guide&lt;/a&gt; explains how policies restrict resource loading and how to test a policy before enforcing it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review framing protection and COOP.&lt;/strong&gt; Choose settings for the app rather than adding headers solely to improve a score. Include these checks when you &lt;a href="https://sitecheckly.com/security-audit" rel="noopener noreferrer"&gt;run a passive security audit&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review cookies and DNS separately.&lt;/strong&gt; Set appropriate SameSite attributes for your cookies. Review CAA, SPF, and DMARC records with whoever manages your domain and email configuration.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add integrity hashes where suitable.&lt;/strong&gt; &lt;a href="https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity" rel="noopener noreferrer"&gt;Subresource Integrity&lt;/a&gt; lets browsers check a fetched resource against an expected hash. It is useful for suitable third-party scripts, but it is not a replacement for reviewing what those scripts do.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A good passive score is not a safety guarantee. It reflects the checks visible to the survey, not a complete assessment of application code, permissions, or runtime behavior.&lt;/p&gt;

&lt;h2&gt;
  
  
  Are Supabase and Firebase safe to use from the browser?
&lt;/h2&gt;

&lt;p&gt;Browser SDK usage and exposed secret credentials are different findings. Treating all client-side backend configuration as a leak makes it harder to identify the problems that need attention.&lt;/p&gt;

&lt;h3&gt;
  
  
  Supabase
&lt;/h3&gt;

&lt;p&gt;In the survey, 55% of apps (262) loaded Supabase directly from the browser. A related finding was that 52% (247) included a Supabase public anon or publishable key in page code. These figures measure different observations and should not be substituted for each other.&lt;/p&gt;

&lt;p&gt;Public anon and publishable keys are intended for client use. Their presence is not evidence that private data is exposed. For a &lt;a href="https://github.com/supabase/supabase" rel="noopener noreferrer"&gt;Supabase application&lt;/a&gt;, the important follow-up is to review the database authorization enforced by Row Level Security, or RLS.&lt;/p&gt;

&lt;p&gt;As the owner, review and test your own policies:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Confirm which tables the client needs to access.&lt;/li&gt;
&lt;li&gt;Check what unauthenticated visitors are permitted to do.&lt;/li&gt;
&lt;li&gt;Test what signed-in users can read and change.&lt;/li&gt;
&lt;li&gt;Confirm that requests outside those permissions are denied.&lt;/li&gt;
&lt;li&gt;Keep service-role keys out of shipped client code.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An outside passive scan cannot see or verify your RLS policies. Finding a public key therefore answers neither “Is the database exposed?” nor “Are the permissions correct?” Those questions require owner-side review and testing.&lt;/p&gt;

&lt;h3&gt;
  
  
  Firebase
&lt;/h3&gt;

&lt;p&gt;The &lt;a href="https://github.com/firebase/firebase-js-sdk" rel="noopener noreferrer"&gt;Firebase JavaScript SDK&lt;/a&gt; supports browser applications. Browser configuration alone is not a substitute for authorization.&lt;/p&gt;

&lt;p&gt;For your own project, review Firebase Security Rules and test both permitted and denied access. Make the expected outcomes explicit before testing, then check that the rules enforce them.&lt;/p&gt;

&lt;p&gt;The survey figures here do not establish a Firebase usage rate. They also do not establish whether any project's authorization rules are correct.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do AI-built apps expose secret keys or call AI APIs directly?
&lt;/h2&gt;

&lt;p&gt;In the survey, 0.2% of apps (1) shipped a secret key in their own page code. Separately, 1.7% (8) called an AI provider API directly from the browser.&lt;/p&gt;

&lt;p&gt;Do not assume these are the same apps. A detected browser API call and a detected secret key are separate findings. The aggregates do not establish that every direct call included a secret credential.&lt;/p&gt;

&lt;p&gt;If a secret appears in shipped client code, treat it as exposed. Removing it from the latest build is not enough to make the old credential safe again. This is a sensitive-information problem, consistent with the risks covered by the &lt;a href="https://owasp.org/www-project-top-10-for-large-language-model-applications/" rel="noopener noreferrer"&gt;OWASP Top 10 for LLM applications&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For your own app:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Remove the credential from client code.&lt;/strong&gt; Check the source and the deployed JavaScript output.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Revoke or rotate it with the provider.&lt;/strong&gt; Do not rely on a code change alone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review the provider's usage records.&lt;/strong&gt; Investigate activity you do not recognize.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Move calls requiring secret credentials to a server-side endpoint.&lt;/strong&gt; Keep those credentials in server-side environment configuration.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Apply authorization and usage limits.&lt;/strong&gt; Treat the endpoint as part of your application's access-control boundary, not just a place to hide a key.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The practical distinction is between configuration intended to be public and credentials that grant privileged access. Fixing the latter takes priority over cosmetic changes to public configuration.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does an exposed AI system prompt mean?
&lt;/h2&gt;

&lt;p&gt;In the survey, 1.5% of apps (7) exposed an AI system prompt in JavaScript.&lt;/p&gt;

&lt;p&gt;A prompt is not inherently a secret. Its exposure becomes more concerning when it contains credentials, sensitive instructions, or rules that the application relies on for security.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://owasp.org/www-project-top-10-for-large-language-model-applications/" rel="noopener noreferrer"&gt;OWASP LLM07, System Prompt Leakage&lt;/a&gt;, warns against treating prompt confidentiality as a security boundary. Instructions telling a model not to reveal information are not a substitute for enforcing access controls in application code.&lt;/p&gt;

&lt;p&gt;Review exposed prompts for what they contain, not just whether they exist:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Remove credentials and other secrets.&lt;/li&gt;
&lt;li&gt;Enforce authorization in application code rather than relying on model instructions.&lt;/li&gt;
&lt;li&gt;Keep sensitive instructions out of shipped client code.&lt;/li&gt;
&lt;li&gt;If a prompt contained a credential, handle that credential as exposed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For your own app, use the free &lt;a href="https://sitecheckly.com/tools/system-prompt-leak-checker" rel="noopener noreferrer"&gt;system prompt leak checker&lt;/a&gt; as a starting point. Follow any finding with a review of the prompt's contents and the application controls around it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How was the survey conducted, and what can it prove?
&lt;/h2&gt;

&lt;p&gt;The fetch took place on 2026-11-08. Of the 560 listed apps in the sample described above, 474 returned a page that could be analyzed. The results therefore describe the analyzed pages, not every listed project or AI-built app.&lt;/p&gt;

&lt;p&gt;The method was passive:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Fetch the home page and up to four of the app's own script files.&lt;/li&gt;
&lt;li&gt;Do not log in.&lt;/li&gt;
&lt;li&gt;Do not make database or API calls.&lt;/li&gt;
&lt;li&gt;Respect robots.txt.&lt;/li&gt;
&lt;li&gt;Do not run JavaScript.&lt;/li&gt;
&lt;li&gt;Report aggregate findings only.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The &lt;a href="https://sitecheckly.com/data/ai-built-apps" rel="noopener noreferrer"&gt;dataset and methodology, available under CC BY 4.0&lt;/a&gt;, provide the basis for the figures and comparisons in this article.&lt;/p&gt;

&lt;p&gt;This approach can identify observable configuration gaps and content present in fetched files. It cannot establish whether RLS or other authorization controls are correct. Code and behavior outside the fetched material remain outside its scope. It also cannot turn an absence of detected leaks into proof that no leaks exist elsewhere.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do next&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Run the &lt;a href="https://sitecheckly.com/tools/ai-app-security-checker" rel="noopener noreferrer"&gt;AI-built app security check&lt;/a&gt; on a page you own. It is free with no sign-up, checks one page per run, and uses a passive security audit.&lt;/li&gt;
&lt;li&gt;Prioritize any exposed secret credentials, then verify backend authorization in your own project.&lt;/li&gt;
&lt;li&gt;Review headers, cookies, DNS records, and suitable third-party script integrity settings.&lt;/li&gt;
&lt;li&gt;After deploying fixes, check the page again and repeat your owner-side permission tests.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does a good security score guarantee an app is safe?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. A passive score reflects observable checks, not a complete review of an app’s code, authorization or runtime behavior.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Should I remove a Supabase public key from my frontend?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A public anon or publishable key is intended for client use. Focus on reviewing and testing RLS policies, and never place a service-role key in client code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does removing a leaked key from the code make it safe again?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Revoke or rotate the exposed key with its provider, then review relevant usage records and replace it with a server-side credential.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>vibecoding</category>
      <category>appsecurity</category>
      <category>securitystatistics</category>
      <category>aiapps</category>
    </item>
    <item>
      <title>Canonical Tags: When to Use Them and What Can Go Wrong</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Tue, 10 Nov 2026 08:41:08 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/canonical-tags-when-to-use-them-and-what-can-go-wrong-59m3</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/canonical-tags-when-to-use-them-and-what-can-go-wrong-59m3</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/canonical-tag-guide" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A canonical tag tells search engines which URL you prefer among duplicate or very similar pages. Use one when several URLs show substantially the same content, or use a self-referencing tag to make your preferred URL explicit. It is a signal, not a guarantee: redirects, noindex directives, and conflicting signals can affect Google’s choice. The recommendations below follow &lt;a href="https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls" rel="noopener noreferrer"&gt;Google’s canonicalization guidance&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is a canonical tag, and why does it matter?
&lt;/h2&gt;

&lt;p&gt;In the survey, &lt;strong&gt;31%&lt;/strong&gt; of analyzed sites had the issue “No canonical URL.” That finding identifies a missing declaration. It does not mean Google cannot select a canonical for those pages.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Survey scope and method:&lt;/strong&gt; These findings come from the October 2026 Sitecheckly survey of the Tranco top 10,000 (Tranco list 7462X). The ranking covers 2026-10-02 to 2026-10-31. Home pages were fetched on 2026-11-01. Analysis was possible for 4,934 of 10,000 domains. The remainder were mostly CDN, DNS and API hosts, sites asking crawlers to stay away in robots.txt, or sites blocking automated requests. See the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;survey methodology&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;A canonical tag lets you nominate the URL you want Google to treat as the representative version of duplicate content. Google still makes the selection. Your declaration helps communicate your preference; it does not force Google to accept it.&lt;/p&gt;

&lt;p&gt;That distinction matters when troubleshooting. A missing tag and an incorrect tag are different problems. Before adding or changing one, decide which URL should represent the content.&lt;/p&gt;

&lt;h2&gt;
  
  
  When do you need a canonical tag?
&lt;/h2&gt;

&lt;p&gt;Use a canonical when different URLs contain duplicate or very similar content. Tracking parameters are a common example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;https://example.com/products/widget
https://example.com/products/widget?utm_source=newsletter
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If both show the same product content, the parameter-free URL can be the preferred canonical.&lt;/p&gt;

&lt;p&gt;A &lt;strong&gt;self-referencing canonical&lt;/strong&gt; points a page to its own preferred URL. It is optional, but it makes that preference explicit. You do not need to invent a different destination just to have a canonical tag.&lt;/p&gt;

&lt;p&gt;Use this decision table with the Google guidance linked above:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Situation&lt;/th&gt;
&lt;th&gt;Canonical approach&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A tracking URL shows the same content as a clean URL&lt;/td&gt;
&lt;td&gt;Point to the clean, preferred URL.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A page is already at its preferred URL&lt;/td&gt;
&lt;td&gt;A self-referencing canonical can make that explicit.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pages contain meaningfully different content&lt;/td&gt;
&lt;td&gt;Do not point them to an unrelated page merely to consolidate URLs.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Equivalent content appears on different domains&lt;/td&gt;
&lt;td&gt;A cross-domain canonical can nominate the preferred version.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A &lt;strong&gt;cross-domain canonical&lt;/strong&gt; uses the same mechanism, but its destination is on another domain. Use it only when the content is equivalent or very similar. As with a same-domain declaration, Google may choose a different URL.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you add a canonical tag?
&lt;/h2&gt;

&lt;p&gt;For an HTML page, put the canonical link element inside the document’s HTML head. This self-referencing example belongs on the preferred product URL:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;head&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;title&amp;gt;&lt;/span&gt;Widget&lt;span class="nt"&gt;&amp;lt;/title&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="na"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"canonical"&lt;/span&gt; &lt;span class="na"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"https://example.com/products/widget"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/head&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On a duplicate tracking URL, use the same &lt;code&gt;href&lt;/code&gt; to nominate the clean product URL. The destination should represent equivalent content, not simply the page you most want to rank.&lt;/p&gt;

&lt;p&gt;Follow Google’s implementation guidance cited above:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use an absolute URL, including the scheme and hostname.&lt;/li&gt;
&lt;li&gt;Put the HTML declaration in the head.&lt;/li&gt;
&lt;li&gt;Keep canonical declarations consistent rather than naming different destinations in different places.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For non-HTML documents, such as PDFs, an HTTP response header is a supported alternative:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="na"&gt;Link: &amp;lt;https://example.com/files/guide.pdf&amp;gt;; rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"canonical"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is a response header, not a line to paste into an HTML page. The HTML element and HTTP header are alternative ways to declare a canonical. Choose the method that fits the resource and your implementation.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should canonical tags do on paginated pages?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Give each paginated page its own canonical URL.&lt;/strong&gt; Do not point every page in a sequence to the first page. Google treats paginated URLs as separate pages, so the later pages should not all nominate the opening page as their canonical. See &lt;a href="https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading" rel="noopener noreferrer"&gt;Google’s pagination guidance&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For example, the page at the following URL should normally reference itself:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;https://example.com/products?page=2
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Its declaration would be:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="na"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"canonical"&lt;/span&gt; &lt;span class="na"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"https://example.com/products?page=2"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Also keep links between paginated pages crawlable. Use ordinary links with an &lt;code&gt;href&lt;/code&gt;, rather than relying only on a button that requires interaction to reveal the next URL.&lt;/p&gt;

&lt;p&gt;The key distinction is content. A tracking parameter may leave the page’s content unchanged. A pagination parameter exposes another part of the sequence. Do not apply the same canonical rule to both without checking what each URL displays. Google’s pagination guidance also distinguishes paginated URLs from alternative filter or sort URLs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which canonical mistakes create conflicting signals?
&lt;/h2&gt;

&lt;p&gt;The following checks come from &lt;a href="https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls" rel="noopener noreferrer"&gt;Google’s guidance on canonical signals and common mistakes&lt;/a&gt;. Conflicts can affect Google’s selection, but they do not guarantee a particular outcome.&lt;/p&gt;

&lt;h3&gt;
  
  
  Mixing noindex and canonical goals
&lt;/h3&gt;

&lt;p&gt;Do not use &lt;code&gt;noindex&lt;/code&gt; as a canonical-selection method. Canonicalization identifies a preferred version; &lt;code&gt;noindex&lt;/code&gt; tells Google not to include the page in search results once Google can crawl and process the directive. These solve different problems. See &lt;a href="https://developers.google.com/search/docs/crawling-indexing/block-indexing" rel="noopener noreferrer"&gt;Google’s noindex documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If your preferred canonical should appear in search, check that it does not carry a &lt;code&gt;noindex&lt;/code&gt; directive. Remove that directive if it conflicts with the page’s intended purpose.&lt;/p&gt;

&lt;h3&gt;
  
  
  Pointing to a URL that redirects
&lt;/h3&gt;

&lt;p&gt;A canonical URL redirect creates an unnecessary mismatch: the tag nominates one URL, while the redirect sends requests elsewhere. Redirects are themselves a canonicalization signal.&lt;/p&gt;

&lt;p&gt;Point the canonical directly to the intended final URL. If the redirect destination is correct, update the source declaration. If the redirect is wrong, fix the redirect before treating its destination as preferred.&lt;/p&gt;

&lt;h3&gt;
  
  
  Naming different preferred URLs
&lt;/h3&gt;

&lt;p&gt;Check for declarations that disagree. For example, an HTML canonical and an HTTP canonical header should not nominate different URLs for the same content.&lt;/p&gt;

&lt;p&gt;Also review internal links and sitemap entries. If your canonical names one URL but those consistently favor another, your signals are not aligned. Make them reflect the same intended destination rather than assuming the tag overrides everything else.&lt;/p&gt;

&lt;h2&gt;
  
  
  How can you check and fix your canonical?
&lt;/h2&gt;

&lt;p&gt;Start with the exact URL you want to investigate. The free &lt;a href="https://sitecheckly.com/tools/canonical-checker" rel="noopener noreferrer"&gt;Sitecheckly canonical checker&lt;/a&gt; helps you review its declared canonical. Each run checks the URL entered, not the whole site.&lt;/p&gt;

&lt;p&gt;Use this troubleshooting sequence:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Confirm the intended destination.&lt;/strong&gt; Does it contain the same or very similar content? Is it the version you want represented in search?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review the declaration.&lt;/strong&gt; Check whether the source URL names that destination and whether another declaration disagrees.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Inspect the destination.&lt;/strong&gt; Check for a redirect or a &lt;code&gt;noindex&lt;/code&gt; directive using the rules above.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fix the source of the conflict.&lt;/strong&gt; Update the HTML tag, HTTP header, redirect, or indexing directive as appropriate.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recheck both URLs.&lt;/strong&gt; Confirm that the original URL and preferred destination now express the intended relationship.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;When the URL is available in Search Console, use &lt;a href="https://support.google.com/webmasters/answer/9012289" rel="noopener noreferrer"&gt;Google’s URL Inspection tool&lt;/a&gt; to compare the user-declared canonical with Google’s selected canonical. Inspect the indexed information for that comparison; a page check alone does not establish which URL Google selected.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do next&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Check a URL where you suspect duplicate content or conflicting signals.&lt;/li&gt;
&lt;li&gt;Write down its intended canonical before changing anything.&lt;/li&gt;
&lt;li&gt;Fix the mismatch, then recheck the source and destination.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does a canonical tag redirect visitors?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. A canonical tag signals a preferred URL to search engines; it does not send visitors to that URL. &lt;a href="https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls" rel="noopener noreferrer"&gt;Google: canonicalization&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a canonical tag appear in the body of a page?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Google supports the canonical link element in the HTML head. Put it there rather than relying on a body declaration. &lt;a href="https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls" rel="noopener noreferrer"&gt;Google: canonicalization&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a sitemap specify canonical URLs?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Google treats URLs included in a sitemap as suggested canonicals, but sitemap inclusion is a weaker signal than a canonical link or redirect. &lt;a href="https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls" rel="noopener noreferrer"&gt;Google: canonicalization&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>canonical</category>
      <category>indexing</category>
      <category>technicalseo</category>
    </item>
    <item>
      <title>PHP Vulnerability October 2026: Check and Fix 2 CVEs</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Mon, 09 Nov 2026 08:25:48 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/php-vulnerability-october-2026-check-and-fix-2-cves-2i19</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/php-vulnerability-october-2026-check-and-fix-2-cves-2i19</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/php-vulnerabilities-exploited-october-2026" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Two PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, are &lt;a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog" rel="noopener noreferrer"&gt;listed by CISA as exploited in the wild&lt;/a&gt;. PHP was detected on 23% of analyzed sites in &lt;a href="https://sitecheckly.com/tech/php" rel="noopener noreferrer"&gt;Sitecheckly’s October 2026 survey&lt;/a&gt;. Check the PHP version used by your application, compare it with the vendor advisory, and apply the vendor’s fixed release or mitigation. If you suspect compromise, follow vendor guidance and investigate.&lt;/p&gt;

&lt;p&gt;For site owners researching a PHP vulnerability October 2026 warning, the important distinction is between detecting PHP and confirming exposure. A technology lookup is a starting point, not a verdict about whether your installation is affected.&lt;/p&gt;

&lt;h2&gt;
  
  
  What are the two PHP vulnerabilities, and which versions are affected?
&lt;/h2&gt;

&lt;p&gt;Both vulnerabilities allow unauthenticated remote code execution, according to the CISA descriptions with their listings. That makes checking your installation and the applicable vendor guidance a priority.&lt;/p&gt;

&lt;h3&gt;
  
  
  CVE-2026-109618: PHP memory corruption
&lt;/h3&gt;

&lt;p&gt;CISA describes CVE-2026-109618 as an out-of-memory corruption vulnerability that allows unauthenticated remote code execution. The &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2026-109618" rel="noopener noreferrer"&gt;CVE-2026-109618 NVD entry&lt;/a&gt; is a reference point for the vulnerability and its linked advisories.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Affected versions: see the vendor advisory.&lt;/strong&gt; Do not assume that every PHP release is affected, or that a release is safe because its version number looks recent.&lt;/p&gt;

&lt;h3&gt;
  
  
  CVE-2026-109619: PHP stale internal request-state
&lt;/h3&gt;

&lt;p&gt;CISA describes CVE-2026-109619 as a stale internal request-state vulnerability that allows unauthenticated remote code execution. Use the &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2026-109619" rel="noopener noreferrer"&gt;CVE-2026-109619 NVD entry&lt;/a&gt; to find the relevant vulnerability references.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Affected versions: see the vendor advisory.&lt;/strong&gt; The survey does not establish affected-version ranges for either CVE.&lt;/p&gt;

&lt;p&gt;For fixed releases and any applicable mitigations, start with &lt;a href="https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching" rel="noopener noreferrer"&gt;CISA’s PHP alert and its vendor references&lt;/a&gt;. Use the vendor’s current guidance rather than guessing a minimum safe version.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why does the CISA KEV listing matter?
&lt;/h2&gt;

&lt;p&gt;Inclusion in the Known Exploited Vulnerabilities catalog means there is evidence of exploitation in the wild. These are not simply theoretical flaws awaiting a possible attack.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog" rel="noopener noreferrer"&gt;CISA added both PHP vulnerabilities on 2026-10-26 and set 2026-10-29 as the action deadline for US federal agencies&lt;/a&gt;. That deadline is not a universal legal requirement for every website owner. Other owners should assess their exposure and act promptly.&lt;/p&gt;

&lt;p&gt;A KEV entry also does not mean your site was hacked. It establishes exploitation of the vulnerability, not compromise of every installation using the software.&lt;/p&gt;

&lt;p&gt;For a related reference, see &lt;a href="https://sitecheckly.com/tech/php/vulnerabilities" rel="noopener noreferrer"&gt;Sitecheckly’s list of PHP vulnerabilities exploited in the wild&lt;/a&gt;. Use it to identify advisories to investigate, not as proof that your own application is affected.&lt;/p&gt;

&lt;h2&gt;
  
  
  How widespread is PHP in the survey?
&lt;/h2&gt;

&lt;p&gt;The October 2026 Sitecheckly survey used the Tranco top 10,000, list 7462X. Its ranking covered 2026-10-02 to 2026-10-31, and home pages were fetched on 2026-11-01. Of 10,000 domains, 4,934 could be analyzed.&lt;/p&gt;

&lt;p&gt;The remaining domains were mostly CDN, DNS and API hosts outside the survey’s scope, sites asking crawlers to stay away through robots.txt, or sites blocking automated requests. The &lt;a href="https://sitecheckly.com/tech/php" rel="noopener noreferrer"&gt;PHP usage page documents the survey context and detection results&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;PHP appeared on 23% of the sites we analyzed, representing 1,130 sites. This describes detected technology in the survey. It does not establish that those sites:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Used a version affected by either CVE.&lt;/li&gt;
&lt;li&gt;Were exposed to the conditions described in the vendor advisory.&lt;/li&gt;
&lt;li&gt;Had been compromised.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Do not use the detection figure as a vulnerability rate. To assess your application, you need its actual PHP version and the advisory that applies to it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How can you check your PHP version?
&lt;/h2&gt;

&lt;p&gt;Start with the application you need to protect. Your goal is to confirm the PHP version it uses, not merely find evidence that PHP exists somewhere in the hosting environment.&lt;/p&gt;

&lt;h3&gt;
  
  
  Check public information
&lt;/h3&gt;

&lt;p&gt;Look at the page source and response headers for a disclosed PHP version. Treat a missing version as inconclusive: it does not prove that PHP is absent or that the application is safe.&lt;/p&gt;

&lt;p&gt;You can also use the free &lt;a href="https://sitecheckly.com/tech-stack" rel="noopener noreferrer"&gt;Sitecheckly tech stack lookup&lt;/a&gt; to check the entered URL for detectable technologies. No sign-up is required. A public lookup may identify PHP without revealing the installed version.&lt;/p&gt;

&lt;p&gt;For a separate check, &lt;a href="https://sitecheckly.com/security-audit" rel="noopener noreferrer"&gt;run Sitecheckly’s passive security audit&lt;/a&gt;. It is also free with no sign-up. The security audit is separate from the home page’s combined SEO and AEO audit.&lt;/p&gt;

&lt;p&gt;Each run covers one page: the URL you enter. It does not scan the whole site or investigate whether a server has been compromised. Do not treat a public audit as confirmation that either PHP CVE is fixed.&lt;/p&gt;

&lt;h3&gt;
  
  
  Confirm the application’s assigned version
&lt;/h3&gt;

&lt;p&gt;Check the hosting control panel or application administration panel for the PHP version assigned to the application. If the panel does not show it, ask the hosting provider to confirm it.&lt;/p&gt;

&lt;p&gt;Keep the request specific:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Which PHP version does this application use?&lt;/li&gt;
&lt;li&gt;Does the vendor advisory identify it as affected by either CVE?&lt;/li&gt;
&lt;li&gt;Which fixed release or mitigation applies?&lt;/li&gt;
&lt;li&gt;Has that fix been deployed to this application’s environment?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Do not publish a diagnostic page that exposes server details just to obtain the version. Prefer the hosting panel or direct confirmation from the provider.&lt;/p&gt;

&lt;p&gt;Once you have the confirmed version, compare it with the vendor advisory. If you cannot establish the applicable version range or fix, keep the issue open rather than marking it resolved from a public lookup alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you fix the flaws and respond to a possible compromise?
&lt;/h2&gt;

&lt;p&gt;Use &lt;a href="https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching" rel="noopener noreferrer"&gt;CISA’s PHP alert&lt;/a&gt; as the starting point for remediation and follow its references to the vendor’s current guidance. For the exact fixed release or mitigation, &lt;strong&gt;see the vendor advisory&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  For self-managed PHP
&lt;/h3&gt;

&lt;p&gt;Confirm whether your installed version is affected. Apply the vendor’s fixed release or the mitigation specified for your installation.&lt;/p&gt;

&lt;p&gt;Keep a record of the advisory you followed, the change made, and the application environment covered. After the change, confirm the version used by the application and check that the application still works as expected.&lt;/p&gt;

&lt;h3&gt;
  
  
  For managed hosting
&lt;/h3&gt;

&lt;p&gt;Ask the provider to confirm the applicable fix and whether it has been deployed. A useful response should address your application’s environment, not just say that the provider takes security seriously.&lt;/p&gt;

&lt;p&gt;If the provider has not completed remediation, ask what vendor-supported mitigation applies and what you need to do. Do not substitute an assumed safe version for a documented answer.&lt;/p&gt;

&lt;h3&gt;
  
  
  If compromise is possible
&lt;/h3&gt;

&lt;p&gt;Follow the vendor’s incident guidance. Review relevant logs, preserve evidence, and rotate potentially exposed credentials. Involve the hosting provider or an incident-response team where appropriate.&lt;/p&gt;

&lt;p&gt;Do not treat installing a PHP security update as the entire incident response. Keep the remediation task and the investigation task separate: you need to address the vulnerable software and investigate any suspected compromise.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do next&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Confirm the PHP version assigned to your application.&lt;/li&gt;
&lt;li&gt;Match it against the vendor advisories for both CVEs.&lt;/li&gt;
&lt;li&gt;Apply or obtain confirmation of the applicable fix.&lt;/li&gt;
&lt;li&gt;If compromise is suspected, preserve evidence and begin an investigation with the appropriate support team.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does a KEV listing mean my site was hacked?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. It means there is evidence that the vulnerability has been exploited in the wild, not that every site using the software was compromised.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is the CISA deadline mandatory for every website owner?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The stated deadline is for US federal agencies. Other owners should assess their exposure and act promptly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can the survey tell me whether my site is vulnerable?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. The survey describes technology detected on sampled home pages; it does not establish the version or security status of your installation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is a passive security audit an incident investigation?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Sitecheckly’s security audit is passive and checks the entered URL. Investigating a possible compromise also requires reviewing relevant logs and following incident-response guidance.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>php</category>
      <category>vulnerabilities</category>
      <category>cisakev</category>
      <category>security</category>
    </item>
    <item>
      <title>Website Security Statistics: October 2026 Survey</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Thu, 05 Nov 2026 08:13:50 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/website-security-statistics-october-2026-survey-40cl</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/website-security-statistics-october-2026-survey-40cl</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/website-security-statistics-october-2026" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The survey found that 6.2% of sites with readable robots.txt files block an AI search crawler, while 15% block a training crawler. Across analyzed home pages, 16% publish llms.txt, and 13% run a detectable end-of-life or vulnerable component. That software figure is a lower bound because detection depends on exposed versions. These findings come from the &lt;a href="https://sitecheckly.com/data" rel="noopener noreferrer"&gt;Sitecheckly open dataset&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The October 2026 Sitecheckly survey used the Tranco top 10,000, list 7462X, covering 2026-10-02 to 2026-10-31. Home pages were fetched on 2026-11-01; 4,934 of 10,000 requested domains could be analyzed. The ranking came from &lt;a href="https://tranco-list.eu" rel="noopener noreferrer"&gt;Tranco&lt;/a&gt;. These are home-page benchmarks, not whole-site assessments.&lt;/p&gt;

&lt;p&gt;Use the website security statistics below to identify checks worth running on your own pages. A common finding is not automatically your most urgent problem. Confirm what applies to your application before changing it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do the website security statistics reveal?
&lt;/h2&gt;

&lt;p&gt;The average security score was &lt;strong&gt;77.1 out of 100&lt;/strong&gt;. The most common missing header was Cross-Origin-Opener-Policy, but the appropriate response depends on what the page does.&lt;/p&gt;

&lt;p&gt;The following shares apply to the analyzed home pages:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Missing header&lt;/th&gt;
&lt;th&gt;Share&lt;/th&gt;
&lt;th&gt;Owner action&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Cross-Origin-Opener-Policy&lt;/td&gt;
&lt;td&gt;95%&lt;/td&gt;
&lt;td&gt;Assess cross-origin isolation needs before choosing a policy.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Referrer-Policy&lt;/td&gt;
&lt;td&gt;73%&lt;/td&gt;
&lt;td&gt;Choose a policy that limits unnecessary URL sharing.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Content-Security-Policy&lt;/td&gt;
&lt;td&gt;66%&lt;/td&gt;
&lt;td&gt;Build and test a policy for the resources the page needs.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;X-Content-Type-Options&lt;/td&gt;
&lt;td&gt;54%&lt;/td&gt;
&lt;td&gt;Set the header to the &lt;code&gt;nosniff&lt;/code&gt; value.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Use the &lt;a href="https://sitecheckly.com/blog/security-headers-list-recommended-values" rel="noopener noreferrer"&gt;security headers guide&lt;/a&gt; for implementation details. A missing header is a configuration finding to assess, not proof of an exploitable vulnerability or a successful attack.&lt;/p&gt;

&lt;p&gt;Two separate findings need their own review:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Third-party scripts without Subresource Integrity: 61%.&lt;/strong&gt; Review eligible static resources and add integrity hashes where appropriate.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No CAA records: 78% of 4,141 sites checked.&lt;/strong&gt; Review whether your DNS should specify authorized certificate authorities.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Do not put script integrity work in the same task as response-header configuration. Give each change an owner and test it against the page's actual dependencies.&lt;/p&gt;

&lt;p&gt;To check your own page, run the free, passive &lt;a href="https://sitecheckly.com/security-audit" rel="noopener noreferrer"&gt;security audit&lt;/a&gt;. It checks the URL entered, requires no sign-up, and does not audit every page on the site.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which software needs maintenance?
&lt;/h2&gt;

&lt;p&gt;The survey detected at least one end-of-life or known-vulnerable component on &lt;strong&gt;13%&lt;/strong&gt; of analyzed home pages. Only common components with exposed versions could be checked, so this is a lower-bound detection figure, not a complete software inventory.&lt;/p&gt;

&lt;p&gt;Each row below uses its own exposed-version sample. End-of-life and known-vulnerability categories can overlap. &lt;strong&gt;Do not add the shares.&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Technology&lt;/th&gt;
&lt;th&gt;Exposed-version sample&lt;/th&gt;
&lt;th&gt;End of life&lt;/th&gt;
&lt;th&gt;Known vulnerability&lt;/th&gt;
&lt;th&gt;Action&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;jQuery&lt;/td&gt;
&lt;td&gt;661 sites&lt;/td&gt;
&lt;td&gt;30%&lt;/td&gt;
&lt;td&gt;44%&lt;/td&gt;
&lt;td&gt;Upgrade and test dependent scripts.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;WordPress&lt;/td&gt;
&lt;td&gt;201 sites&lt;/td&gt;
&lt;td&gt;0.0%&lt;/td&gt;
&lt;td&gt;3.5%&lt;/td&gt;
&lt;td&gt;Update core and verify compatibility.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Font Awesome&lt;/td&gt;
&lt;td&gt;147 sites&lt;/td&gt;
&lt;td&gt;45%&lt;/td&gt;
&lt;td&gt;0.0%&lt;/td&gt;
&lt;td&gt;Move to a supported release.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Nginx&lt;/td&gt;
&lt;td&gt;146 sites&lt;/td&gt;
&lt;td&gt;70%&lt;/td&gt;
&lt;td&gt;57%&lt;/td&gt;
&lt;td&gt;Check vendor support and patch status.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Drupal&lt;/td&gt;
&lt;td&gt;135 sites&lt;/td&gt;
&lt;td&gt;7.4%&lt;/td&gt;
&lt;td&gt;0.0%&lt;/td&gt;
&lt;td&gt;Update core and modules.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PHP&lt;/td&gt;
&lt;td&gt;110 sites&lt;/td&gt;
&lt;td&gt;42%&lt;/td&gt;
&lt;td&gt;42%&lt;/td&gt;
&lt;td&gt;Upgrade the runtime and test the application.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Bootstrap&lt;/td&gt;
&lt;td&gt;95 sites&lt;/td&gt;
&lt;td&gt;52%&lt;/td&gt;
&lt;td&gt;41%&lt;/td&gt;
&lt;td&gt;Upgrade and test layouts and scripts.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;An advisory match needs verification. A Linux distribution may backport a security fix without changing the exposed version string, which can make version-based risk estimates too high. Conversely, a component that exposes no version may escape these checks. The &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt; explains these detection limits.&lt;/p&gt;

&lt;p&gt;For your own maintenance queue, record the detected version, the installed package's patch status, and the team responsible for the upgrade. Do not treat a hidden version as evidence that software is current.&lt;/p&gt;

&lt;h2&gt;
  
  
  How ready are sites for AI search?
&lt;/h2&gt;

&lt;p&gt;The average AI-search readiness score was &lt;strong&gt;66.4 out of 100&lt;/strong&gt;. The survey found gaps in structured data and in how pages presented answers.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Finding&lt;/th&gt;
&lt;th&gt;Share&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;No Organization schema&lt;/td&gt;
&lt;td&gt;72%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No concise answer-first paragraphs detected&lt;/td&gt;
&lt;td&gt;70%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No question-style subheadings&lt;/td&gt;
&lt;td&gt;68%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No Schema.org structured data found&lt;/td&gt;
&lt;td&gt;51%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Treat these as review prompts, not a template every page must follow. Use accurate, relevant structured data. Put a direct answer near the start when the page addresses a question. Use question-style headings when they make the content easier to navigate, not simply to satisfy a check.&lt;/p&gt;

&lt;p&gt;The free &lt;a href="https://sitecheckly.com/aeo-audit" rel="noopener noreferrer"&gt;AEO audit&lt;/a&gt; checks the URL entered and can help identify these findings. Passing the checks does not guarantee an AI-search citation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;llms.txt adoption was 16%.&lt;/strong&gt; That is an adoption measure, not a requirement for visibility. The file remains a proposal, and major engines have not committed to reading it. Google's &lt;a href="https://developers.google.com/search/docs/appearance/ai-features" rel="noopener noreferrer"&gt;guidance for AI features in Search&lt;/a&gt; says no new AI text files are needed to appear in those features. Keep that distinction in mind when reviewing &lt;a href="https://sitecheckly.com/blog/ai-crawlers-list-user-agents" rel="noopener noreferrer"&gt;AI crawler access and related files&lt;/a&gt;: publishing an optional file should not displace work on intended crawler access or useful page content.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which AI crawlers do sites block?
&lt;/h2&gt;

&lt;p&gt;Among the &lt;strong&gt;4,546 sites with readable robots.txt&lt;/strong&gt;, &lt;strong&gt;6.2%&lt;/strong&gt; blocked at least one AI search crawler, compared with &lt;strong&gt;15%&lt;/strong&gt; blocking at least one training crawler. In that same group, &lt;strong&gt;9.2%&lt;/strong&gt; blocked training crawlers while allowing AI search crawlers.&lt;/p&gt;

&lt;p&gt;These AI crawler blocking statistics show why a blanket “AI bots allowed or blocked” label is not precise enough. Search access and training permissions need separate decisions.&lt;/p&gt;

&lt;p&gt;Reported blocking shares for selected agents were:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;User agent&lt;/th&gt;
&lt;th&gt;Share blocking it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;CCBot&lt;/td&gt;
&lt;td&gt;12%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Bytespider&lt;/td&gt;
&lt;td&gt;11%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GPTBot&lt;/td&gt;
&lt;td&gt;11%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ClaudeBot&lt;/td&gt;
&lt;td&gt;10%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google-Extended&lt;/td&gt;
&lt;td&gt;9.3%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;All shares in this table use the readable-robots.txt group, not every analyzed home page.&lt;/p&gt;

&lt;p&gt;Check the purpose of each agent before changing policy:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;OAI-SearchBot&lt;/strong&gt; supports ChatGPT search citations. &lt;strong&gt;GPTBot&lt;/strong&gt; is for OpenAI model training. &lt;strong&gt;ChatGPT-User&lt;/strong&gt; fetches content on a user's request. These are distinct roles in the &lt;a href="https://platform.openai.com/docs/bots" rel="noopener noreferrer"&gt;OpenAI bot documentation&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Claude-SearchBot&lt;/strong&gt; is a search crawler, while &lt;strong&gt;ClaudeBot&lt;/strong&gt; is a training crawler. &lt;strong&gt;PerplexityBot&lt;/strong&gt; is Perplexity's crawler. The &lt;a href="https://sitecheckly.com/blog/ai-crawlers-list-user-agents" rel="noopener noreferrer"&gt;AI crawlers guide&lt;/a&gt; separates these user agents and their purposes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google-Extended&lt;/strong&gt; controls Gemini training, not Google Search or AI Overviews. Googlebot handles Search crawling. See &lt;a href="https://developers.google.com/crawling/docs/crawlers-fetchers/overview-google-crawlers" rel="noopener noreferrer"&gt;Google's crawler overview&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Blocking a search crawler can affect that engine's ability to fetch content. Allowing it does not promise inclusion or citations.&lt;/p&gt;

&lt;p&gt;Write down your intended policy, then test representative URLs against the actual robots.txt rules. Under &lt;a href="https://datatracker.ietf.org/doc/html/rfc9309" rel="noopener noreferrer"&gt;RFC 9309&lt;/a&gt;, the longest matching rule wins. Do not assume that the first rule in the file decides the result.&lt;/p&gt;

&lt;h2&gt;
  
  
  What SEO and technology maintenance should owners prioritize?
&lt;/h2&gt;

&lt;p&gt;The website SEO statistics point to several practical page-level checks:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Finding&lt;/th&gt;
&lt;th&gt;Share&lt;/th&gt;
&lt;th&gt;Owner action&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Images missing alt text&lt;/td&gt;
&lt;td&gt;61%&lt;/td&gt;
&lt;td&gt;Write useful alternatives where needed.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Title length outside the recommended range&lt;/td&gt;
&lt;td&gt;49%&lt;/td&gt;
&lt;td&gt;Review titles for clarity rather than length alone.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No h1 found&lt;/td&gt;
&lt;td&gt;34%&lt;/td&gt;
&lt;td&gt;Add a descriptive main heading where appropriate.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No canonical URL&lt;/td&gt;
&lt;td&gt;31%&lt;/td&gt;
&lt;td&gt;Review canonicalization and the intended preferred URL.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Run the free &lt;a href="https://sitecheckly.com/seo-audit" rel="noopener noreferrer"&gt;SEO audit&lt;/a&gt; on the URL you want to review. Use the results to investigate the page, not to make automatic edits without context.&lt;/p&gt;

&lt;p&gt;The survey also detected these CMS shares:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;CMS&lt;/th&gt;
&lt;th&gt;Share of analyzed home pages&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;WordPress&lt;/td&gt;
&lt;td&gt;12%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Drupal&lt;/td&gt;
&lt;td&gt;3.6%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Adobe Experience Manager&lt;/td&gt;
&lt;td&gt;2.4%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are detection shares, not a complete CMS census. Maintain your own platform inventory and name a maintenance owner for each system. That inventory should be more authoritative than what an external home-page check can identify.&lt;/p&gt;

&lt;p&gt;There is also a separate front-end dependency finding: &lt;strong&gt;31% of 680 sites exposing a jQuery version ran jQuery 1.x or 2.x&lt;/strong&gt;. This is a different version-exposing group from the software-health table above.&lt;/p&gt;

&lt;p&gt;Use that finding as a prompt to inventory front-end dependencies, plan upgrades, and test compatibility. Keep the two jQuery samples separate when comparing results or reporting progress.&lt;/p&gt;

&lt;h2&gt;
  
  
  How was the survey conducted, and what are its limits?
&lt;/h2&gt;

&lt;p&gt;The survey analyzed home-page responses fetched over HTTP or HTTPS, without rendering JavaScript. It also included checks beyond those responses, such as DNS CAA records. It respected robots.txt. Domains that could not be analyzed were mostly CDN, DNS and API hosts, sites asking crawlers to stay away, or sites blocking automated requests.&lt;/p&gt;

&lt;p&gt;The scope and fetch dates are stated near the top of this report. The &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt; describes the collection approach and its limits.&lt;/p&gt;

&lt;p&gt;Read the benchmarks with these constraints in mind:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Page scope:&lt;/strong&gt; a home-page finding does not establish the condition of every page on a domain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Different denominators:&lt;/strong&gt; robots.txt findings, CAA checks, and software-specific results use the groups stated beside them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Detection limits:&lt;/strong&gt; exposed-version checks provide lower-bound detection shares, while advisory matches can overstate risk where fixes were backported.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No individual-site claims:&lt;/strong&gt; this report presents aggregates and names no individual sites.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No proof of compromise:&lt;/strong&gt; a configuration finding or version match is a reason to investigate, not evidence that an attack succeeded.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The reported figures and denominators are available in the &lt;a href="https://sitecheckly.com/data" rel="noopener noreferrer"&gt;open dataset, licensed under CC BY 4.0&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do next&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Choose an important URL and audit that page. Sitecheckly is free with no sign-up.&lt;/li&gt;
&lt;li&gt;Use the home page for SEO and AEO together, or choose a dedicated audit. Security is a separate audit.&lt;/li&gt;
&lt;li&gt;Verify software findings against your inventory and vendor patch information.&lt;/li&gt;
&lt;li&gt;Assign each confirmed fix to an owner, test the change, and rerun the relevant page audit.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does a missing security header mean a site is compromised?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. A missing header is a configuration finding, not evidence that an attack has succeeded. Its importance depends on the application and the protection the header would provide.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a site block training crawlers without blocking AI search crawlers?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes. Operators can write separate robots.txt rules for different user agents, then check that the rules reflect their intended policy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does an exposed vulnerable version prove the installation is unpatched?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. A distribution may backport a security fix without changing the version string used for detection. Check the vendor's patch information before assessing the risk.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can Sitecheckly audit every page in a site at once?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Each run audits the single URL entered. The security audit is separate from the SEO and AEO audits.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>securitystatistics</category>
      <category>aisearch</category>
      <category>seo</category>
      <category>websitemaintenance</category>
    </item>
    <item>
      <title>AI Crawlers List: Training vs. Search User Agents</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Tue, 03 Nov 2026 09:41:24 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/ai-crawlers-list-training-vs-search-user-agents-1p9h</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/ai-crawlers-list-training-vs-search-user-agents-1p9h</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/ai-crawlers-list-user-agents" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;AI crawlers serve different purposes. Blocking &lt;a href="https://platform.openai.com/docs/bots" rel="noopener noreferrer"&gt;GPTBot targets training access, while blocking OAI-SearchBot affects ChatGPT search&lt;/a&gt;. The same distinction applies to &lt;a href="https://support.anthropic.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web" rel="noopener noreferrer"&gt;ClaudeBot and Claude-SearchBot&lt;/a&gt;. &lt;a href="https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers" rel="noopener noreferrer"&gt;Google-Extended controls Gemini training, not Google Search or AI Overviews&lt;/a&gt;. Choose robots.txt rules by purpose rather than blocking every AI-related user agent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why does blocking training differ from blocking AI search?
&lt;/h2&gt;

&lt;p&gt;In the survey, 9.2% of sites blocked training crawlers while still allowing AI search crawlers. That is a useful distinction if you want to limit training access without closing off search discovery.&lt;/p&gt;

&lt;p&gt;The November 2026 Sitecheckly survey covered the Tranco top 10,000, using Tranco list 7462X. We could analyze 4,934 of 10,000 domains. The rest were mostly CDN, DNS and API hosts, sites that ask crawlers to stay away in robots.txt, or sites that blocked automated requests. The training-versus-search finding uses the 4,546 sites with a readable robots.txt. See the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;survey methodology&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Treat your crawler policy as separate decisions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Training:&lt;/strong&gt; May an operator crawl your content for model training?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Search:&lt;/strong&gt; May a search crawler access your pages for search-related use?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User-requested access:&lt;/strong&gt; May a service fetch a page when someone explicitly asks for it?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A training opt-out is not the same as a search opt-out. Start with the outcome you want, then choose the matching user-agent groups.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which AI crawler user agents should you know?
&lt;/h2&gt;

&lt;p&gt;This AI crawlers list separates training, search and user-requested fetching. Google-Extended is included because it belongs in the policy decision, even though it is a control token rather than a separate fetching crawler.&lt;/p&gt;

&lt;p&gt;The allow and block columns describe the whole-site patterns shown below. They are alternatives, not instructions to apply both.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;User-agent token&lt;/th&gt;
&lt;th&gt;Operator&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;th&gt;Allow rule&lt;/th&gt;
&lt;th&gt;Block rule&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;GPTBot&lt;/td&gt;
&lt;td&gt;OpenAI&lt;/td&gt;
&lt;td&gt;Model training&lt;/td&gt;
&lt;td&gt;Allow all paths&lt;/td&gt;
&lt;td&gt;Disallow all paths&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;OAI-SearchBot&lt;/td&gt;
&lt;td&gt;OpenAI&lt;/td&gt;
&lt;td&gt;ChatGPT search&lt;/td&gt;
&lt;td&gt;Allow all paths&lt;/td&gt;
&lt;td&gt;Disallow all paths&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ChatGPT-User&lt;/td&gt;
&lt;td&gt;OpenAI&lt;/td&gt;
&lt;td&gt;Fetching on a user's request&lt;/td&gt;
&lt;td&gt;Allow all paths*&lt;/td&gt;
&lt;td&gt;Disallow all paths*&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ClaudeBot&lt;/td&gt;
&lt;td&gt;Anthropic&lt;/td&gt;
&lt;td&gt;Model training&lt;/td&gt;
&lt;td&gt;Allow all paths&lt;/td&gt;
&lt;td&gt;Disallow all paths&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Claude-SearchBot&lt;/td&gt;
&lt;td&gt;Anthropic&lt;/td&gt;
&lt;td&gt;Search&lt;/td&gt;
&lt;td&gt;Allow all paths&lt;/td&gt;
&lt;td&gt;Disallow all paths&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PerplexityBot&lt;/td&gt;
&lt;td&gt;Perplexity&lt;/td&gt;
&lt;td&gt;Search&lt;/td&gt;
&lt;td&gt;Allow all paths&lt;/td&gt;
&lt;td&gt;Disallow all paths&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google-Extended&lt;/td&gt;
&lt;td&gt;Google&lt;/td&gt;
&lt;td&gt;Gemini training control, not a separate crawler&lt;/td&gt;
&lt;td&gt;Allow all paths&lt;/td&gt;
&lt;td&gt;Disallow all paths&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;For &lt;strong&gt;OAI-SearchBot vs GPTBot&lt;/strong&gt;, the key difference is search versus training. ChatGPT-User is separate from both: it fetches content in response to a user's request. &lt;em&gt;OpenAI notes that robots.txt rules may not apply to these user-initiated requests, so a ChatGPT-User block is not a guaranteed access restriction.&lt;/em&gt; See &lt;a href="https://platform.openai.com/docs/bots" rel="noopener noreferrer"&gt;OpenAI's bot documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For Anthropic, use the distinct tokens for distinct decisions: &lt;a href="https://support.anthropic.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web" rel="noopener noreferrer"&gt;ClaudeBot is for training, while Claude-SearchBot supports search&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://docs.perplexity.ai/guides/bots" rel="noopener noreferrer"&gt;PerplexityBot is Perplexity's search crawler&lt;/a&gt;. Do not classify it as a training crawler just because it is associated with an AI service.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you allow or block an AI crawler in robots.txt?
&lt;/h2&gt;

&lt;p&gt;Use a user-agent group to name the crawler, then add the path rule. In these examples, the root path covers the whole site under that robots.txt policy. The group and path matching rules come from &lt;a href="https://datatracker.ietf.org/doc/html/rfc9309" rel="noopener noreferrer"&gt;RFC 9309&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;To block AI training access through GPTBot:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;User-agent: GPTBot
Disallow: /
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To allow AI search access through OAI-SearchBot:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;User-agent: OAI-SearchBot
Allow: /
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;These groups can coexist. Blocking GPTBot does not require blocking OAI-SearchBot.&lt;/p&gt;

&lt;h3&gt;
  
  
  Allow patterns for the listed tokens
&lt;/h3&gt;

&lt;p&gt;Each group below expresses an allow-all policy for its named token. Select the groups that match your intended policy. The ChatGPT-User caveat above still applies.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Block patterns for the listed tokens
&lt;/h3&gt;

&lt;p&gt;These are the equivalent disallow-all groups. This is a reference, not a recommended file to paste wholesale. Blocking every listed search crawler would work against a policy intended to preserve AI search access.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;User-agent: GPTBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-SearchBot
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Google-Extended
Disallow: /
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For a training-blocked, search-allowed policy, select the block groups for GPTBot, ClaudeBot and Google-Extended. Select the allow groups for OAI-SearchBot, Claude-SearchBot and PerplexityBot. Make the user-requested access decision separately.&lt;/p&gt;

&lt;h3&gt;
  
  
  Check group selection and path precedence
&lt;/h3&gt;

&lt;p&gt;Do not assume that the last line in the file wins. Under &lt;a href="https://datatracker.ietf.org/doc/html/rfc9309" rel="noopener noreferrer"&gt;RFC 9309's matching rules&lt;/a&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A crawler uses the groups matching its product token. Matching groups for that token are combined.&lt;/li&gt;
&lt;li&gt;The wildcard group is the fallback when no specific user-agent group matches. Its rules are not automatically added to a matching specific group.&lt;/li&gt;
&lt;li&gt;Within the applicable rules, the longest matching path wins.&lt;/li&gt;
&lt;li&gt;When equivalent allow and disallow rules match, the allow rule should be used.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example, this group blocks GPTBot from the site except for the more specific public path:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;User-agent: GPTBot
Disallow: /
Allow: /public/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;An allow rule is permission under the robots.txt policy. It is not a promise that a service will crawl, use or cite the page. Keep access eligibility separate from the goal of earning a citation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Does Google-Extended affect Google Search or AI Overviews?
&lt;/h2&gt;

&lt;p&gt;No. To opt out of Gemini training through this control, use:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;User-agent: Google-Extended
Disallow: /
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Google-Extended is a robots.txt control token. It is not a separate crawler making requests under that name. Blocking it does not block Google Search or AI Overviews; Googlebot is the relevant Search crawler. See &lt;a href="https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers" rel="noopener noreferrer"&gt;Google's crawler documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Do not substitute a Googlebot block when your intended decision is only about Gemini training. Those controls address different purposes.&lt;/p&gt;

&lt;h2&gt;
  
  
  How can you check a page after changing crawler rules?
&lt;/h2&gt;

&lt;p&gt;Start with the published robots.txt, not just the copy in your editor. Compare its user-agent groups with the policy you meant to publish.&lt;/p&gt;

&lt;p&gt;Use this checklist:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Training policy:&lt;/strong&gt; Are GPTBot, ClaudeBot and Google-Extended treated as intended?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Search policy:&lt;/strong&gt; Are OAI-SearchBot, Claude-SearchBot and PerplexityBot allowed or blocked deliberately?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User-requested access:&lt;/strong&gt; Have you considered ChatGPT-User separately, including its enforcement limitation?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rule matching:&lt;/strong&gt; Does the page's path match a more specific exception?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google policy:&lt;/strong&gt; Have you kept the Google-Extended decision separate from Googlebot access?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then run the free, no-sign-up &lt;a href="https://sitecheckly.com/aeo-audit" rel="noopener noreferrer"&gt;Sitecheckly AEO audit&lt;/a&gt; on the page URL. Each run audits one page: the URL you enter, not the whole site.&lt;/p&gt;

&lt;p&gt;For context beyond crawler access, read the &lt;a href="https://sitecheckly.com/blog/what-is-answer-engine-optimization" rel="noopener noreferrer"&gt;answer engine optimization explainer&lt;/a&gt;. Use it to separate the access question from the broader work of making a page useful in search answers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do next&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Write down your training, search and user-requested access decisions.&lt;/li&gt;
&lt;li&gt;Publish only the groups that express those decisions.&lt;/li&gt;
&lt;li&gt;Check the published rules against the specific page you want assessed.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is ChatGPT-User the same as OAI-SearchBot?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. ChatGPT-User fetches content in response to a user's request; OAI-SearchBot supports ChatGPT search. See &lt;a href="https://platform.openai.com/docs/bots" rel="noopener noreferrer"&gt;OpenAI's bot documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does allowing an AI search crawler guarantee a citation?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. An allow rule permits crawling under that robots.txt policy; it does not guarantee that a service will crawl, use or cite the page.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What happens if two robots.txt path rules conflict?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The most specific matching path wins. If equivalent allow and disallow rules match, the protocol says the allow rule should be used. See &lt;a href="https://datatracker.ietf.org/doc/html/rfc9309" rel="noopener noreferrer"&gt;RFC 9309&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>aicrawlers</category>
      <category>robotstxt</category>
      <category>aeo</category>
      <category>useragents</category>
    </item>
    <item>
      <title>Content Security Policy Example: Start in Report-Only</title>
      <dc:creator>Hieu Le</dc:creator>
      <pubDate>Tue, 03 Nov 2026 08:19:23 +0000</pubDate>
      <link>https://dev.to/hieu_le_f3630aa13143b35d8/content-security-policy-example-start-in-report-only-1dm6</link>
      <guid>https://dev.to/hieu_le_f3630aa13143b35d8/content-security-policy-example-start-in-report-only-1dm6</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://sitecheckly.com/blog/content-security-policy-example-report-only" rel="noopener noreferrer"&gt;Sitecheckly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Start with a &lt;code&gt;Content-Security-Policy-Report-Only&lt;/code&gt; header that restricts resources to your own origin. Test the page, review browser console violations, and adjust the policy before enforcing it. Report-only mode lets you find what the policy would block without blocking those resources. &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy-Report-Only" rel="noopener noreferrer"&gt;MDN explains the report-only behavior&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Survey method
&lt;/h2&gt;

&lt;p&gt;The November 2026 Sitecheckly survey examined the Tranco top 10,000, using Tranco list 7462X. Analysis was possible for 4,934 of 10,000 domains. The others were mostly CDN, DNS and API hosts, sites whose robots.txt asked crawlers to stay away, or sites that blocked automated requests. Among the analyzed sites, 66% were missing CSP. See the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;survey methodology&lt;/a&gt; for scope and limitations.&lt;/p&gt;

&lt;p&gt;That finding is a reason to check your response headers, not a reason to copy an enforcing policy into production without testing.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does a starter Content Security Policy do?
&lt;/h2&gt;

&lt;p&gt;CSP tells the browser which sources a page may use for resources such as scripts, styles and images. It can reduce the impact of cross-site scripting by restricting which code may execute. It is an additional defense, not a substitute for fixing injection flaws. See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP" rel="noopener noreferrer"&gt;MDN’s CSP guide&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This content security policy example is a starting point for a page that serves its scripts and styles from its own origin:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The value uses &lt;code&gt;'self'&lt;/code&gt; for the page’s own origin. The image rule also permits data URLs through &lt;code&gt;data:&lt;/code&gt;. Keep that colon: &lt;code&gt;data'&lt;/code&gt; is not the correct source expression. These source expressions and directives are documented in the &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy" rel="noopener noreferrer"&gt;CSP header reference&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This is deliberately a small baseline. It is not a policy guaranteed to fit your page, and it is not a complete hardening policy. Expect to review anything loaded from another origin, along with inline code.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does CSP report-only mode work?
&lt;/h2&gt;

&lt;p&gt;A report-only policy observes violations without enforcing its restrictions. A resource can therefore load successfully while still producing a violation. Read that message as “this would violate the proposed policy,” not “this resource was blocked.” See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy-Report-Only" rel="noopener noreferrer"&gt;MDN’s report-only reference&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Use this testing sequence:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Open browser developer tools and select the Console and Network panels.&lt;/li&gt;
&lt;li&gt;Reload the page and inspect the document’s response headers.&lt;/li&gt;
&lt;li&gt;Confirm that the intended report-only header is present.&lt;/li&gt;
&lt;li&gt;Exercise menus, forms, search, media and other interactive features.&lt;/li&gt;
&lt;li&gt;Record each violation, the resource involved and the feature that needs it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Test logged-in flows and third-party integrations too. A clean test of a public landing page does not establish that checkout, account pages or embedded tools are ready.&lt;/p&gt;

&lt;p&gt;The starter header above does not configure a report collector. If you want reports delivered to a service, set up a working reporting endpoint and the relevant reporting directive. For example, &lt;code&gt;report-uri&lt;/code&gt; names an endpoint that receives violation reports, though it is deprecated. Review &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/report-uri" rel="noopener noreferrer"&gt;MDN’s reporting guidance&lt;/a&gt; before choosing a reporting setup.&lt;/p&gt;

&lt;p&gt;Do not assume reports are being stored just because the header is present. Verify delivery at your collector separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which CSP directives should you check first?
&lt;/h2&gt;

&lt;p&gt;Start with the resource types most likely to affect visible features:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Directive&lt;/th&gt;
&lt;th&gt;What to investigate&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;script-src&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;External scripts, inline script blocks and inline event handlers.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;style-src&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;External stylesheets, inline style blocks and style attributes.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;img-src&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Images from other origins and any data URLs the page uses.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;default-src&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Resource types without their own explicit fetch directive.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;code&gt;default-src&lt;/code&gt; is a fallback for fetch directives that are not explicitly set. In this baseline, review fonts, connections and frames as well as scripts and styles. When you define a specific fetch directive, its source list takes the place of that fallback for the resource type. These behaviors are covered in the &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy" rel="noopener noreferrer"&gt;CSP directive reference&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For each violation, ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does the page still need this resource?&lt;/li&gt;
&lt;li&gt;Which feature depends on it?&lt;/li&gt;
&lt;li&gt;Is the reported origin the source you intended to trust?&lt;/li&gt;
&lt;li&gt;Can you remove the dependency instead of expanding the policy?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep a short record of each allowed source and its purpose. That makes later reviews easier than reconstructing why an origin was added.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you add the policy in Nginx?
&lt;/h2&gt;

&lt;p&gt;Place this directive inside the relevant existing &lt;code&gt;server&lt;/code&gt; or &lt;code&gt;location&lt;/code&gt; block:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nginx"&gt;&lt;code&gt;&lt;span class="k"&gt;add_header&lt;/span&gt; &lt;span class="s"&gt;Content-Security-Policy-Report-Only&lt;/span&gt; &lt;span class="s"&gt;"default-src&lt;/span&gt; &lt;span class="s"&gt;'self'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;script-src&lt;/span&gt; &lt;span class="s"&gt;'self'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;style-src&lt;/span&gt; &lt;span class="s"&gt;'self'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="k"&gt;img-src&lt;/span&gt; &lt;span class="s"&gt;'self'&lt;/span&gt; &lt;span class="s"&gt;data:"&lt;/span&gt; &lt;span class="s"&gt;always&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;always&lt;/code&gt; parameter applies the header regardless of the response status code. Header inheritance depends on configuration context, so check for other &lt;code&gt;add_header&lt;/code&gt; directives in nested blocks rather than assuming this setting reaches every response. See the &lt;a href="https://nginx.org/en/docs/http/ngx_http_headers_module.html#add_header" rel="noopener noreferrer"&gt;Nginx headers module documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Before considering the change deployed:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Check the Nginx configuration for errors.&lt;/li&gt;
&lt;li&gt;Reload Nginx after the check succeeds.&lt;/li&gt;
&lt;li&gt;Request the public page and inspect its actual response headers.&lt;/li&gt;
&lt;li&gt;Check relevant routes that use different location blocks.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Inspect the response the browser receives, not just the configuration file you edited.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you add the policy in Apache?
&lt;/h2&gt;

&lt;p&gt;With &lt;code&gt;mod_headers&lt;/code&gt; enabled, add this directive to the applicable server or virtual-host configuration:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight apache"&gt;&lt;code&gt;&lt;span class="nc"&gt;Header&lt;/span&gt; &lt;span class="ss"&gt;always&lt;/span&gt; &lt;span class="ss"&gt;set&lt;/span&gt; Content-Security-Policy-Report-Only "default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Apache’s &lt;code&gt;Header&lt;/code&gt; directive supports the &lt;code&gt;always&lt;/code&gt; condition shown here. Its documentation also explains how header tables can lead to duplicate headers, especially when other components set them. See the &lt;a href="https://httpd.apache.org/docs/2.4/mod/mod_headers.html" rel="noopener noreferrer"&gt;Apache mod_headers documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Check the configuration, reload Apache, then inspect the public response. Look for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A missing report-only header.&lt;/li&gt;
&lt;li&gt;Duplicate CSP headers.&lt;/li&gt;
&lt;li&gt;An existing enforced policy that you did not intend to change.&lt;/li&gt;
&lt;li&gt;Different header values on different routes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If another application or proxy already sets CSP, identify which layer should own the policy before adding another configuration.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you move from reports to enforcement?
&lt;/h2&gt;

&lt;p&gt;Investigate violations individually. Do not turn the console output into an automatic allowlist.&lt;/p&gt;

&lt;p&gt;Remove unnecessary dependencies first. Then allow only the sources the page actually needs. Avoid adding broad permissions just to make the messages disappear.&lt;/p&gt;

&lt;p&gt;For inline scripts, consider a nonce- or hash-based approach instead of broadly allowing inline code. A nonce must be generated for each response and applied to the intended script elements; a hash must match the allowed script content. These approaches require changes beyond copying a static header. Follow the &lt;a href="https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html" rel="noopener noreferrer"&gt;OWASP CSP implementation guidance&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Once the reviewed policy passes your functional tests, deploy its value under &lt;code&gt;Content-Security-Policy&lt;/code&gt; instead of relying only on report-only mode. Repeat the same tests after enforcement. Do not promote the starter value unchanged unless your testing shows it fits the page.&lt;/p&gt;

&lt;p&gt;Keep reviewing violations as dependencies and page features change. If you want collected reports after enforcement, retain a working reporting configuration in the enforced policy.&lt;/p&gt;

&lt;h3&gt;
  
  
  What to do next
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Run the free &lt;a href="https://sitecheckly.com/security-audit" rel="noopener noreferrer"&gt;Sitecheckly security audit&lt;/a&gt;. It passively checks security headers on the single URL you enter, with no sign-up. It does not replace browser interaction testing.&lt;/li&gt;
&lt;li&gt;Test other representative pages separately before deploying a shared policy across them.&lt;/li&gt;
&lt;li&gt;Review the &lt;a href="https://sitecheckly.com/blog/security-headers-list-recommended-values" rel="noopener noreferrer"&gt;security headers guide&lt;/a&gt; for related headers that need their own configuration decisions.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Can CSP replace output encoding?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Treat CSP as defense in depth, not a replacement for preventing injection. See the &lt;a href="https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html" rel="noopener noreferrer"&gt;OWASP CSP cheat sheet&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can an enforced policy and a report-only policy run together?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes. You can enforce one policy while testing another in report-only mode. See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy-Report-Only" rel="noopener noreferrer"&gt;MDN's report-only reference&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does CSP prevent other sites from embedding my page?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;frame-ancestors&lt;/code&gt; directive can control which parents may embed a page. Add it explicitly if embedding restrictions are needed; it does not fall back to &lt;code&gt;default-src&lt;/code&gt;. See &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/frame-ancestors" rel="noopener noreferrer"&gt;MDN's frame-ancestors reference&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;Want to see how your own site does? Run a free audit at &lt;a href="https://sitecheckly.com/?utm_source=devto" rel="noopener noreferrer"&gt;sitecheckly.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figures in this article come from Sitecheckly's own audit data; see the &lt;a href="https://sitecheckly.com/methodology" rel="noopener noreferrer"&gt;methodology&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>csp</category>
      <category>securityheaders</category>
      <category>nginx</category>
      <category>apache</category>
    </item>
  </channel>
</rss>
