dnnsoftware
[Enhancement]: AEO setting
Is there an existing issue for this?
- [x] I have searched the existing issues
Description of problem
The usage of Chatgpt and other AI bots changes the customer journey. So we need to be able to make a choice: will we allow chatbots to crawl the content? But also: if they can. in what way? Is AI allowed to paraphrase? Or is the content very delicate and only in full citation.
Description of solution
In line with SEO settings, we need AEO settings. Meaning we want to influence the way our content is treated by AI. What I have in mind is a new tab 'AEO'
Clicking that tab shows an option list (or other selection method that offers the options
Full free use – This content may be freely used. This writes in the HEAD of the page
No use – This content may not be reused by AI or search engines. This writes in the HEAD of the page
Only in its entirety – May not be used in fragments or rewritten. This writes in the HEAD of the page
Only with attribution – Use is permitted provided the original source is credited. This writes in the HEAD of the page
Description of alternatives considered
You can manually add the values in the head of a page. But we need to have something for editors. So, a dropdown
Anything else?
No response
Do you plan to contribute code for this enhancement?
- [ ] Yes
Would you be interested in sponsoring this enhancement?
- [ ] Yes
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Is there any type of defined standard yet for this? Or a working proposal for one? This seems more like a discussion than an Issue right now, but obviously very interesting!
This is the closest I've seen: https://vercel.com/blog/a-proposal-for-inline-llm-instructions-in-html
But definitely not yet a standard.
I think we need to have at least it be a published standard before we add something, the removal of features that never make it to true life ae very hard to manage from an expectation/maintenance perspective.
We need to be sure to be responsive to things so timing is a bit hard to judge.
Ideally, ther would be a list with 2 columns. The name that is shown in the dropdown The value that is written in the head.
It will take quite a bit of time beofre w3c wil formalize things. Untill then some bots will be more progressive and responsive to these meta tags. Other will follow later or even ignore.
There are 2 things:
- It would be easy to maintain for editors/ webmasters. No need for code change
- It would underline that DNN is at the forefront of the AI era
We have started using LLMS.txt files in the root. HOWEVER, there has yet to evolve as a "standard" per se. It reminds me of the early days of sitemap.xml. For a long time it was not considered a "standard".
That said, I am in favor of holding off until a true standard evolves.
Maybe, as an alertnative, is to make this part of an "Experiemental" settings grouping that is something disabled by default and maybe subject to different standards for support, removal, etc.