In this guide
- Training and grounding answer different questions
- Where each preference belongs
- Dates for sites already using NoArchive or NoCache
- An implementation example—not a recommendation to block
- Six checks before deploying a preference
- A worked example for a UAE service business
- Do not confuse the controls with a ranking tactic
- Practical questions
- Need a controlled website change?
Decide what you want to allow before changing any crawler setting. Microsoft announced separate AI training and grounding preferences on 30 October 2026. It says honouring them begins on 1 February 2027 as it crawls—not on the announcement date. Microsoft’s announcement.
A business can have different views about model training and using its public pages to inform an answer. Record those choices separately, assign an owner and test the implementation. Do not copy a blocking rule merely because it is described as “AI SEO”.

Training and grounding answer different questions
Training concerns using content to change a generative model’s learned parameters. Grounding concerns using it as input when generating a response. Microsoft’s preferences are independent; both default to Allow. The new choices do not change eligibility for traditional Bing results, but normal crawling and indexing rules still apply. Source: Microsoft.
For a service business, start with a plain-language decision: “We want people to find our public advice, but we need to decide how it can be reused.” Then separate marketing, intellectual-property and confidentiality concerns. Private quotations, customer documents and account records should be protected by access controls, not treated as public marketing pages with a preference tag attached.
Where each preference belongs
| Use | Where it is expressed | Choices |
|---|---|---|
| AI training | robots.txt for a site or path; a page meta tag or HTTP header can override it for that page. | Allow or Disallow. |
| AI grounding | Page meta tag or HTTP header—not robots.txt. | Allow, DisallowExtended or Disallow. |
DisallowExtended limits grounding to Microsoft-operated experiences and excludes grounding services Microsoft supplies to third parties. Microsoft’s page-level controls apply to Microsoft; they are not universal instructions for every AI service. Source: Bing Webmaster documentation.
A developer therefore needs a decision for the content category, not just a request to “add the AI code”. Public service pages, an advice library and licensed material may require different treatment. Document intentional exceptions so the next redesign does not overwrite them.
Dates for sites already using NoArchive or NoCache
The transition matters particularly to existing users of those legacy settings. Microsoft gives this sequence: official transition instructions.
| Date | What to plan |
|---|---|
| 15 December 2026 | Temporary grounding preferences open in Bing Webmaster Tools for sites using NoArchive or NoCache as of that date. |
| 1 February 2027 | New preferences begin taking effect as Microsoft crawls. |
| Before 1 March 2027 | Existing restriction users should publish the new training preference. To maintain grounding restrictions, publish page preferences and record the temporary Webmaster Tools preference. |
| 30 September 2027 | Temporary grounding preferences expire, or end earlier when the new page preference is discovered. There is no temporary training setting. |
Put the decision and technical review ahead of the deadline. A developer can confirm that a tag is served; that alone does not confirm a crawler has revisited it. Keep the change date, sample URLs and observed responses in the handover record.
An implementation example—not a recommendation to block
The following is Microsoft’s page-level syntax for disallowing training. It belongs in the affected page’s HTML head:
<meta name="Bingbot" content="ai-training:disallow">A separate grounding restriction would use:
<meta name="Bingbot" content="ai-grounding:disallow">Use only the setting approved for that page. An Allow preference does not override a crawl block. The shared robots.txt training approach is based on IETF work in progress, not a finished universal standard. Source and alternative HTTP-header examples.
These code samples are explanatory text. Reading this article does not apply them to your website. No training or grounding restriction has been added to UVs Digital Hub as part of this article.

Six checks before deploying a preference
1. List the actual places a directive can be set
Check the HTML head, HTTP response headers, robots.txt, hosting rules and any CDN settings. Record the responsible owner for each layer. On a custom HTML site, one correct page does not prove every page was updated; on a CMS, a global template can affect more pages than intended.
2. Agree a content-category decision
Choose representative service pages, articles and downloads. For each category, write the intended training treatment, intended grounding treatment, owner and reason. Escalate licensed material to the person who understands the rights agreement. A marketing preference is not a substitute for that review.
3. Test an ordinary page and an exception
Use a staging copy. Inspect both page source and response headers after the change. Check an article with the general policy, one with an intentional exception, a service page and an error page. Confirm that no unrelated noindex or crawler-wide restriction was added.
4. Check the deployment, not only the ZIP
Compare the intended file with what the server returns. An extra extraction folder, an old cache or a later template build can leave the live page different from the approved source. Preserve your PHP endpoints, analytics and existing redirect rules during this narrow change.
5. Keep implementation and discovery evidence separate
Your test record should have two columns: “served by the website” and “subsequently observed by the crawler”, with dates where evidence exists. Leave the second unresolved until it can be checked. Do not mark a change complete just because a developer committed a file.
6. Record a rollback and a future check
Keep the previous files and the policy decision together. Name the person who can reverse an accidental broad restriction. Review the official instructions again before deployment and before the transition milestones, because a future-dated announcement can change.
A worked example for a UAE service business
Imagine a consultancy with public service pages and technical articles. It decides to restrict training for its public advice while leaving grounding at its default. This is a fictional planning example, not a UVs customer policy or a recommendation for every business.
The acceptance test should prove that the selected preference is present on the intended articles, the service pages retain their approved treatment, and ordinary search directives are unchanged. The developer also checks whether an older template or response header introduces a conflicting instruction.
After upload, the owner checks a small sample of live URLs and records the result. A reviewer signs off the implementation against the written decision. Traffic changes in the following week are not proof that this setting caused a gain or loss: other page, campaign and search changes may be involved.
UVs Digital Hub uses individual HTML page files alongside shared assets and a PHP audit endpoint. That makes file-to-live comparison and a page inventory practical checks. It does not establish how Bing has processed a particular release, and it is not evidence of an AI-visibility result.
Do not confuse the controls with a ranking tactic
Google separately says its normal SEO fundamentals apply to AI Overviews and AI Mode: there is no special schema or additional optimisation requirement for inclusion. Eligibility is not a guarantee of appearance. Google Search Central.
For the website itself, continue writing useful answers, keeping claims supported and making contact paths usable. Review actual enquiries rather than treating a permission setting as a growth strategy. Our website audit checklist covers wider checks, while the AI Mode advertising guide addresses the separate paid-advertising question.
Practical questions
Should my developer change every page immediately?
Start with an approved policy and an inventory. A blanket change is difficult to review when different parts of the site have different purposes or rights arrangements. Test a representative sample and intentional exceptions before a wider deployment.
What should I send for a technical review?
Share the public hostname, representative URLs, current directive examples, hosting/CDN details and the intended business policy. Do not send private keys, customer files or administrative credentials in an ordinary enquiry message.
Need a controlled website change?
UVs Digital Hub can help scope technical SEO and website maintenance work around the current setup, the approved decision and a test plan. Discuss the requirement before changing crawler settings across an entire site.
Sources and scope
Prepared 2 November 2026. The Microsoft announcement and FAQ are linked next to their relevant guidance; the dates are announced future milestones, not a claim that they are already live. The implementation checklist and fictional example are editorial recommendations. No licensing, legal, traffic or ranking outcome is promised.
