Duplicate Listings
Would like to suggest consideration to identifying duplicate/similar listings as we are finding many users submitting multiple listings with identical/similar content . This tends to occur with personnel changes @sponsors with no idea a listing exists. Also when importing listings froma Dbase can also create a multiple listing situation

J C 8 days ago
Duplicate Listings
Would like to suggest consideration to identifying duplicate/similar listings as we are finding many users submitting multiple listings with identical/similar content . This tends to occur with personnel changes @sponsors with no idea a listing exists. Also when importing listings froma Dbase can also create a multiple listing situation

J C 8 days ago
Internal Admin Notes for All Content Types
I think it would be very useful to add an Admin Notes / Internal Notes feature across all content types within eDirectory. This should apply to: Listings Deals Events Classifieds Articles Blog Forum Banners The purpose would be to allow administrators to record important internal information directly against any piece of content. These notes would be visible only to administrators and never visible publicly or to the account owner. For example: Suspended – 11 September 2026, 10:35 AM Content suspended following repeated attempts to add information that does not meet our requirements. Account owner contacted by email. Other examples could include: Verification Required – Business ownership needs to be confirmed. Complaint Received – Complaint received regarding information published in this listing. Banner Issue – Advertiser supplied incorrect artwork; waiting for replacement. Duplicate Content – Possible duplicate of another listing. Needs review before approval. Admin Note History Rather than having a single note that gets overwritten, I think each content item should have an internal history of notes. Each entry could automatically record: Date and time Administrator who added the note Note Optional status/reason For example: 11 Sep – Aaron: Listing suspended. Verification requested. 12 Sep – Lilian: Documents received from business owner. 13 Sep – Aaron: Verification completed and listing reinstated. This creates a simple internal administrative history for that content. Display in the Content Management Screens The feature would be particularly useful if Admin Notes could be displayed as a column in the existing Content management screens. For example: Title Status Admin Notes ABC Plumbing Active Verification completed... XYZ Services Suspended Suspended – duplicate busin... Only the beginning of the latest note needs to be displayed so it does not take up too much space. The administrator could hover over the text to see the full latest note, or click it/Edit to open the complete Admin Notes history. Admin Notes should also be searchable, making it possible to search for words such as: Suspended, Complaint, Verification, Duplicate, Warning, Ownership, Fraud, Payment, etc. Why This Would Be Useful As a directory grows, it becomes increasingly dif

Aaron B 8 days ago
Internal Admin Notes for All Content Types
I think it would be very useful to add an Admin Notes / Internal Notes feature across all content types within eDirectory. This should apply to: Listings Deals Events Classifieds Articles Blog Forum Banners The purpose would be to allow administrators to record important internal information directly against any piece of content. These notes would be visible only to administrators and never visible publicly or to the account owner. For example: Suspended – 11 September 2026, 10:35 AM Content suspended following repeated attempts to add information that does not meet our requirements. Account owner contacted by email. Other examples could include: Verification Required – Business ownership needs to be confirmed. Complaint Received – Complaint received regarding information published in this listing. Banner Issue – Advertiser supplied incorrect artwork; waiting for replacement. Duplicate Content – Possible duplicate of another listing. Needs review before approval. Admin Note History Rather than having a single note that gets overwritten, I think each content item should have an internal history of notes. Each entry could automatically record: Date and time Administrator who added the note Note Optional status/reason For example: 11 Sep – Aaron: Listing suspended. Verification requested. 12 Sep – Lilian: Documents received from business owner. 13 Sep – Aaron: Verification completed and listing reinstated. This creates a simple internal administrative history for that content. Display in the Content Management Screens The feature would be particularly useful if Admin Notes could be displayed as a column in the existing Content management screens. For example: Title Status Admin Notes ABC Plumbing Active Verification completed... XYZ Services Suspended Suspended – duplicate busin... Only the beginning of the latest note needs to be displayed so it does not take up too much space. The administrator could hover over the text to see the full latest note, or click it/Edit to open the complete Admin Notes history. Admin Notes should also be searchable, making it possible to search for words such as: Suspended, Complaint, Verification, Duplicate, Warning, Ownership, Fraud, Payment, etc. Why This Would Be Useful As a directory grows, it becomes increasingly dif

Aaron B 8 days ago
Make Tier Changes One-Click — Keep Sponsors, Grow Revenue
We need a simple way for Sponsors to upgrade or downgrade their subscription tier without having to create a new listing. This affects every directory owner’s bottom line: A Sponsor ready to upgrade = more revenue — unless changing tiers means starting over. A Sponsor who needs a cheaper tier can keep paying something — instead of cancelling and paying $0. Less back-and-forth = less admin for us and less frustration for Sponsors. But there’s an even bigger issue: Sponsors can lose everything they’ve built on their listing. If changing tiers means creating a new listing, they don’t just have to rewrite their content. They can also lose their star ratings, reviews and testimonials — the social proof they may have spent months or years building would be gone. Why would a Sponsor risk losing all of that just to upgrade? And if they need to downgrade, we’re making the decision to leave even easier. Why rebuild from scratch on the same directory, losing their social proof when they can simply cancel? That creates unnecessary friction at exactly the moment we’re trying to retain or grow a paying Sponsor. Sponsors should be able to choose a new tier, click, done — while keeping their existing listing, content, ratings, reviews and testimonials intact. We shouldn’t make it easier to leave than to stay. Easy upgrades and downgrades are core functionality for a subscription directory. They mean more upgrades, fewer cancellations, protected Sponsor value, happier Sponsors, and more recurring revenue for directory owners. If keeping Sponsors and growing directory revenue matters to you too, please VOTE for this feature.

Terryk about 1 month ago
Make Tier Changes One-Click — Keep Sponsors, Grow Revenue
We need a simple way for Sponsors to upgrade or downgrade their subscription tier without having to create a new listing. This affects every directory owner’s bottom line: A Sponsor ready to upgrade = more revenue — unless changing tiers means starting over. A Sponsor who needs a cheaper tier can keep paying something — instead of cancelling and paying $0. Less back-and-forth = less admin for us and less frustration for Sponsors. But there’s an even bigger issue: Sponsors can lose everything they’ve built on their listing. If changing tiers means creating a new listing, they don’t just have to rewrite their content. They can also lose their star ratings, reviews and testimonials — the social proof they may have spent months or years building would be gone. Why would a Sponsor risk losing all of that just to upgrade? And if they need to downgrade, we’re making the decision to leave even easier. Why rebuild from scratch on the same directory, losing their social proof when they can simply cancel? That creates unnecessary friction at exactly the moment we’re trying to retain or grow a paying Sponsor. Sponsors should be able to choose a new tier, click, done — while keeping their existing listing, content, ratings, reviews and testimonials intact. We shouldn’t make it easier to leave than to stay. Easy upgrades and downgrades are core functionality for a subscription directory. They mean more upgrades, fewer cancellations, protected Sponsor value, happier Sponsors, and more recurring revenue for directory owners. If keeping Sponsors and growing directory revenue matters to you too, please VOTE for this feature.

Terryk about 1 month ago
Adding the Claim Listing Feature to the Mobile App
I love the eDirectory platform, including the mobile app functions. However, I think it would be great to add the “claim listing” feature to the mobile app version of the directory. I am really promoting usage of the app and I’d like to make sure that this feature is available to users-particularly those listed in the directory. Having this would further protect the directory

Plenary Assets Admin about 1 month ago
Adding the Claim Listing Feature to the Mobile App
I love the eDirectory platform, including the mobile app functions. However, I think it would be great to add the “claim listing” feature to the mobile app version of the directory. I am really promoting usage of the app and I’d like to make sure that this feature is available to users-particularly those listed in the directory. Having this would further protect the directory

Plenary Assets Admin about 1 month ago
Feature Request: Short-Form Video Support for Listing and Event Pages
Request Please add native support for short-form vertical videos on individual Listing and Event pages, including: YouTube Shorts TikTok Instagram Reels Facebook Reels Ideally, this functionality should be integrated into the existing Listing/Event video player, allowing a short-form video URL to be added in the same way YouTube or Vimeo videos are currently supported. If extending the existing player is not technically practical, a dedicated Short-Form Video widget or field for Listing and Event pages would be an excellent alternative. Current Limitation eDirectory currently supports traditional YouTube/Vimeo video content on listings, but YouTube Shorts and other major short-form video formats cannot be used in the same way. Version 14 introduced a carousel widget supporting TikTok and YouTube Shorts for general pages, which was a valuable addition. However, this does not address the original use case: associating a short-form video directly with an individual Listing or Event. The short video should represent that specific business, attraction, destination, restaurant, hotel, activity, or event rather than being part of a general site-wide video carousel. Why This Matters Short-form vertical video has become one of the primary ways people discover businesses, destinations, attractions, restaurants, activities, and events online. For a directory, a visitor often does not need or want a long promotional video. A 30 to 60-second video can quickly show: what the place looks like; what visitors can expect; the atmosphere or experience; key attractions, products, or services; why someone may want to visit. This is particularly valuable for tourism and local directories, where visual presentation can have a major influence on a visitor's decision. Short-form video is also now routinely created for YouTube Shorts, TikTok, Instagram Reels, and Facebook Reels. Allowing directory owners and advertisers to reuse this existing content would significantly increase the value and relevance of Listing and Event pages. Suggested Implementation Preferred option: Extend the existing Listing/Event YouTube/Vimeo video functionality to recognize and properly display supported short-form URLs from: YouTube Shorts TikTok Instagram Reels Facebook Reels The player should preserve the appropriate vertical aspect ratio rather than forcing vertical content into a traditional 16:9 player. Alternative option: Introduce a dedicated Short-Form Video field/widget for Listing and Event pages that accepts supported URLs and renders the appropriate vertical player. Ideally, the implementation should also be responsive and optimized for mobile devices. Summary The general-page Shorts carousel introduced in v14 is useful, but it solves a different use case

Lurquilla about 1 month ago
Feature Request: Short-Form Video Support for Listing and Event Pages
Request Please add native support for short-form vertical videos on individual Listing and Event pages, including: YouTube Shorts TikTok Instagram Reels Facebook Reels Ideally, this functionality should be integrated into the existing Listing/Event video player, allowing a short-form video URL to be added in the same way YouTube or Vimeo videos are currently supported. If extending the existing player is not technically practical, a dedicated Short-Form Video widget or field for Listing and Event pages would be an excellent alternative. Current Limitation eDirectory currently supports traditional YouTube/Vimeo video content on listings, but YouTube Shorts and other major short-form video formats cannot be used in the same way. Version 14 introduced a carousel widget supporting TikTok and YouTube Shorts for general pages, which was a valuable addition. However, this does not address the original use case: associating a short-form video directly with an individual Listing or Event. The short video should represent that specific business, attraction, destination, restaurant, hotel, activity, or event rather than being part of a general site-wide video carousel. Why This Matters Short-form vertical video has become one of the primary ways people discover businesses, destinations, attractions, restaurants, activities, and events online. For a directory, a visitor often does not need or want a long promotional video. A 30 to 60-second video can quickly show: what the place looks like; what visitors can expect; the atmosphere or experience; key attractions, products, or services; why someone may want to visit. This is particularly valuable for tourism and local directories, where visual presentation can have a major influence on a visitor's decision. Short-form video is also now routinely created for YouTube Shorts, TikTok, Instagram Reels, and Facebook Reels. Allowing directory owners and advertisers to reuse this existing content would significantly increase the value and relevance of Listing and Event pages. Suggested Implementation Preferred option: Extend the existing Listing/Event YouTube/Vimeo video functionality to recognize and properly display supported short-form URLs from: YouTube Shorts TikTok Instagram Reels Facebook Reels The player should preserve the appropriate vertical aspect ratio rather than forcing vertical content into a traditional 16:9 player. Alternative option: Introduce a dedicated Short-Form Video field/widget for Listing and Event pages that accepts supported URLs and renders the appropriate vertical player. Ideally, the implementation should also be responsive and optimized for mobile devices. Summary The general-page Shorts carousel introduced in v14 is useful, but it solves a different use case

Lurquilla about 1 month ago
Articles
For me, having an article section is a big part of my site SEO and monetization. If there could be a level assignment similar to listings and events, that could be very useful

Paul Jackson about 1 month ago
Articles
For me, having an article section is a big part of my site SEO and monetization. If there could be a level assignment similar to listings and events, that could be very useful

Paul Jackson about 1 month ago
Feature Enhancement Request: Related Listings Widget
Hello eDirectory Team, First, I'd like to thank your for continuing to improve the platform. I've been building a tourism directory and have found the Related Listings widget to be a valuable feature. D uring implementation, however, I identified an enhancement that I believe would greatly increase its flexibility while remaining fully backward compatible. Current Limitation The Related Listings widget currently supports three display methods: By Category By Location By Category & Location When By Category or By Category & Location is selected, the widget automatically displays listings from the same category as the page where the widget is placed. Likewise, when By Location or By Category & Location is selected, the widget automatically uses the same location as the current listing. While this works well for traditional "related listings," it prevents site owners from displaying complementary content from other categories or locations without custom development. Proposed Enhancement Add two optional override fields to the existing widget configuration. Override Category (Optional) Display this field whenever: By Category By Category & Location is selected. The field would present a dropdown containing all available listing categories. Behavior If left blank, the widget behaves exactly as it does today by using the current listing's category. If a category is selected, the widget displays listings from the selected category instead. Override Location (Optional) Display this field whenever: By Location By Category & Location is selected. The field would allow the administrator to select a specific location. Behavior If left blank, the widget behaves exactly as it does today by using the current listing's location. If a location is selected, the widget displays listings from that selected location instead. Suggested Configuration Display Method □ By Category □ By Location □ By Category & Location Override Category (Optional) [Dropdown] Override Location (Optional) [Dropdown] Sort By [Highest Rated] Number of Listings [10] If either override field is left empty, the widget simply falls back to its current behavior. Backward Compatibility One of the biggest advantages of this enhancement is that it is completely optional. Existing websites require no changes. Existing widgets continue to function exactly as they do today. Site owners only use the new functionality when desired. No existing implementations wo

Lurquilla about 2 months ago
Feature Enhancement Request: Related Listings Widget
Hello eDirectory Team, First, I'd like to thank your for continuing to improve the platform. I've been building a tourism directory and have found the Related Listings widget to be a valuable feature. D uring implementation, however, I identified an enhancement that I believe would greatly increase its flexibility while remaining fully backward compatible. Current Limitation The Related Listings widget currently supports three display methods: By Category By Location By Category & Location When By Category or By Category & Location is selected, the widget automatically displays listings from the same category as the page where the widget is placed. Likewise, when By Location or By Category & Location is selected, the widget automatically uses the same location as the current listing. While this works well for traditional "related listings," it prevents site owners from displaying complementary content from other categories or locations without custom development. Proposed Enhancement Add two optional override fields to the existing widget configuration. Override Category (Optional) Display this field whenever: By Category By Category & Location is selected. The field would present a dropdown containing all available listing categories. Behavior If left blank, the widget behaves exactly as it does today by using the current listing's category. If a category is selected, the widget displays listings from the selected category instead. Override Location (Optional) Display this field whenever: By Location By Category & Location is selected. The field would allow the administrator to select a specific location. Behavior If left blank, the widget behaves exactly as it does today by using the current listing's location. If a location is selected, the widget displays listings from that selected location instead. Suggested Configuration Display Method □ By Category □ By Location □ By Category & Location Override Category (Optional) [Dropdown] Override Location (Optional) [Dropdown] Sort By [Highest Rated] Number of Listings [10] If either override field is left empty, the widget simply falls back to its current behavior. Backward Compatibility One of the biggest advantages of this enhancement is that it is completely optional. Existing websites require no changes. Existing widgets continue to function exactly as they do today. Site owners only use the new functionality when desired. No existing implementations wo

Lurquilla about 2 months ago
Sticky (Floating) Sidebar for Listing Detail Pages
Hello Team, I would like to suggest adding an optional Sticky (Floating) Sidebar feature for Listing Detail Pages. Current Situation On listing pages containing substantial content such as descriptions, videos, image galleries, reviews, nearby attractions, and other information, the right sidebar is only visible near the top of the page. Once visitors begin scrolling through the content, important sidebar elements disappear from view and remain inaccessible unless the user manually scrolls back to the top of the page. This is particularly noticeable on longer listings where users spend significant time reading and exploring content. Proposed Enhancement Introduce an optional Sticky (Floating) Sidebar that remains visible as users scroll through the page. The sidebar would stay within the visible viewport while respecting the page layout and automatically stop when reaching the end of the content area. This behavior is commonly found on modern travel, directory, real estate, e-commerce, and hospitality websites because it keeps key actions accessible throughout the user's browsing experience. Elements That Would Benefit A sticky sidebar could keep the following items visible throughout the page: Reservation and booking buttons Contact and inquiry buttons Maps and directions Social media links Nearby listings and recommendations Promotional widgets Advertising placements Other sidebar widgets configured by the site owner Benefits Improved User Experience Eliminates the need to scroll back to the top to access important actions. Creates a smoother and more intuitive browsing experience. Improves usability on long-form content pages. Increased Conversion Opportunities Reservation, booking, contact, and inquiry buttons remain visible at all times. Visitors can take action the moment they decide to engage. May increase lead generation and conversion rates for listing owners. Improved Advertising Visibility Sidebar advertisements remain visible for a greater portion of the visit. Potential increase in ad impressions and click-through rates. Better Engagement Across the Platform Maps, social links, and nearby recommendations remain easily accessible. Encourages visitors to explore additional listings and content. Suggested Configuration To maximize flexibility, consider making this a configurable option within the widget or page settings, allowing administrators to choose between: Standard Sidebar Sticky (Floating) Sidebar This would enable site owners to select the behavior that best fits their design and user experience goals. Additional Consideration Before implementing a completely new feature, it may be worth confirming whether the platform or theme framework already supports sticky widgets or sticky sidebars internally and simply does not expose the option within the current settings interface. If such functionality already exists, exposing it as a configurable setting could provide a quick and efficient enhancement with minimal development effort. Use Cases This feature would be particularly valuable for: Tourism attractions Restaurants Hotels and accommodations Event venues Tour operators Activity providers Long-form directory listings with extensive c

Lurquilla 3 months ago
Sticky (Floating) Sidebar for Listing Detail Pages
Hello Team, I would like to suggest adding an optional Sticky (Floating) Sidebar feature for Listing Detail Pages. Current Situation On listing pages containing substantial content such as descriptions, videos, image galleries, reviews, nearby attractions, and other information, the right sidebar is only visible near the top of the page. Once visitors begin scrolling through the content, important sidebar elements disappear from view and remain inaccessible unless the user manually scrolls back to the top of the page. This is particularly noticeable on longer listings where users spend significant time reading and exploring content. Proposed Enhancement Introduce an optional Sticky (Floating) Sidebar that remains visible as users scroll through the page. The sidebar would stay within the visible viewport while respecting the page layout and automatically stop when reaching the end of the content area. This behavior is commonly found on modern travel, directory, real estate, e-commerce, and hospitality websites because it keeps key actions accessible throughout the user's browsing experience. Elements That Would Benefit A sticky sidebar could keep the following items visible throughout the page: Reservation and booking buttons Contact and inquiry buttons Maps and directions Social media links Nearby listings and recommendations Promotional widgets Advertising placements Other sidebar widgets configured by the site owner Benefits Improved User Experience Eliminates the need to scroll back to the top to access important actions. Creates a smoother and more intuitive browsing experience. Improves usability on long-form content pages. Increased Conversion Opportunities Reservation, booking, contact, and inquiry buttons remain visible at all times. Visitors can take action the moment they decide to engage. May increase lead generation and conversion rates for listing owners. Improved Advertising Visibility Sidebar advertisements remain visible for a greater portion of the visit. Potential increase in ad impressions and click-through rates. Better Engagement Across the Platform Maps, social links, and nearby recommendations remain easily accessible. Encourages visitors to explore additional listings and content. Suggested Configuration To maximize flexibility, consider making this a configurable option within the widget or page settings, allowing administrators to choose between: Standard Sidebar Sticky (Floating) Sidebar This would enable site owners to select the behavior that best fits their design and user experience goals. Additional Consideration Before implementing a completely new feature, it may be worth confirming whether the platform or theme framework already supports sticky widgets or sticky sidebars internally and simply does not expose the option within the current settings interface. If such functionality already exists, exposing it as a configurable setting could provide a quick and efficient enhancement with minimal development effort. Use Cases This feature would be particularly valuable for: Tourism attractions Restaurants Hotels and accommodations Event venues Tour operators Activity providers Long-form directory listings with extensive c

Lurquilla 3 months ago
Planned
Serve Markdown content on Accept: text/markdown requests for full AI Content score - Part 2
Following on from the llms.txt feature request — once llms.txt and llms-full.txt are in place, the remaining gap to a full score on the Content dimension of isitagentready.com is Markdown content negotiation. When an AI agent requests a page, it sends an Accept: text/markdown header. If your server returns HTML, the agent has to parse out navigation, scripts, ads, and markup noise to get to the actual content — burning tokens and often getting it wrong. If your server detects that header and returns clean Markdown instead, the agent gets exactly what it needs, efficiently. The request: When eDirectory detects an Accept: text/markdown request header, return a clean Markdown version of the page instead of HTML — covering at minimum: Category pages (name, description, listing summaries) Listing detail pages (business name, description, contact info, category) Key static pages (About, Contact, Add a Listing) This doesn't need to replace the HTML response for normal browsers — just intercept the header and serve an alternate clean representation to agents that ask for it. Why it matters: This is the difference between an AI agent being able to read your directory and being able to use it as a reliable source. Combined with llms.txt, a proper robots.txt with AI bot rules, and a sitemap, this completes the first three AI readiness categories and puts eDirectory sites at the top of the scoring curve. Most platforms haven't implemented this yet. It's a genuine differentiator right now. Aaron

Aaron B 3 months ago
Planned
Serve Markdown content on Accept: text/markdown requests for full AI Content score - Part 2
Following on from the llms.txt feature request — once llms.txt and llms-full.txt are in place, the remaining gap to a full score on the Content dimension of isitagentready.com is Markdown content negotiation. When an AI agent requests a page, it sends an Accept: text/markdown header. If your server returns HTML, the agent has to parse out navigation, scripts, ads, and markup noise to get to the actual content — burning tokens and often getting it wrong. If your server detects that header and returns clean Markdown instead, the agent gets exactly what it needs, efficiently. The request: When eDirectory detects an Accept: text/markdown request header, return a clean Markdown version of the page instead of HTML — covering at minimum: Category pages (name, description, listing summaries) Listing detail pages (business name, description, contact info, category) Key static pages (About, Contact, Add a Listing) This doesn't need to replace the HTML response for normal browsers — just intercept the header and serve an alternate clean representation to agents that ask for it. Why it matters: This is the difference between an AI agent being able to read your directory and being able to use it as a reliable source. Combined with llms.txt, a proper robots.txt with AI bot rules, and a sitemap, this completes the first three AI readiness categories and puts eDirectory sites at the top of the scoring curve. Most platforms haven't implemented this yet. It's a genuine differentiator right now. Aaron

Aaron B 3 months ago
Planned
Add llms.txt and llms-full.txt support for AI agent readiness - Part 1
AI agents (ChatGPT, Claude, Perplexity, Gemini) are increasingly how people find businesses and services — and they need a different signal than Google does. The emerging standard is llms.txt and llms-full.txt, two plain Markdown files served from your web root that give AI agents a clean, structured map of your site — what it covers, your main categories, key pages. Think of it as robots.txt but for LLMs. The spec is documented at llmstxt.org. Cloudflare recently launched a free AI readiness scanner at isitagentready.com that scores your site 0–100 across five dimensions. The llms.txt files directly impact the Content score. Without them, AI agents have to scrape HTML and often skip the site entirely. The request: Add a dedicated AI Identity section in the eDirectory admin panel where directory owners can provide: Directory name and tagline Purpose and description of the directory Who the directory is for (target audience) What regions, industries, or niches it covers When the directory was founded/launched Primary contact name and email Owner/operator website or social links Auto-generate llms.txt and llms-full.txt by combining that AI Identity information with the directory's live category structure, key pages, and site description — similar to how sitemaps are already generated Serve both files from the web root with correct Content-Type: text/plain headers and keep them updated as categories and pages change The AI Identity section is important because auto-generating from categories alone gives AI agents the structure of the directory but not the context — who runs it, why it exists, who it serves. That context is what helps an AI agent decide whether your directory is the right source to cite for a given query. For sites already on Cloudflare, this would also push scores significantly on isitagentready.com. Worth noting that full marks on the Content dimension also requires serving Markdown on Accept: text/markdown requests, which could be a natural follow-on feature. See Part 2 This is a quick win that puts eDirectory sites ahead of the vast majority of the web right now. The window where this is a differentiator rather than table stakes won't be open long. Aaron

Aaron B 3 months ago
Planned
Add llms.txt and llms-full.txt support for AI agent readiness - Part 1
AI agents (ChatGPT, Claude, Perplexity, Gemini) are increasingly how people find businesses and services — and they need a different signal than Google does. The emerging standard is llms.txt and llms-full.txt, two plain Markdown files served from your web root that give AI agents a clean, structured map of your site — what it covers, your main categories, key pages. Think of it as robots.txt but for LLMs. The spec is documented at llmstxt.org. Cloudflare recently launched a free AI readiness scanner at isitagentready.com that scores your site 0–100 across five dimensions. The llms.txt files directly impact the Content score. Without them, AI agents have to scrape HTML and often skip the site entirely. The request: Add a dedicated AI Identity section in the eDirectory admin panel where directory owners can provide: Directory name and tagline Purpose and description of the directory Who the directory is for (target audience) What regions, industries, or niches it covers When the directory was founded/launched Primary contact name and email Owner/operator website or social links Auto-generate llms.txt and llms-full.txt by combining that AI Identity information with the directory's live category structure, key pages, and site description — similar to how sitemaps are already generated Serve both files from the web root with correct Content-Type: text/plain headers and keep them updated as categories and pages change The AI Identity section is important because auto-generating from categories alone gives AI agents the structure of the directory but not the context — who runs it, why it exists, who it serves. That context is what helps an AI agent decide whether your directory is the right source to cite for a given query. For sites already on Cloudflare, this would also push scores significantly on isitagentready.com. Worth noting that full marks on the Content dimension also requires serving Markdown on Accept: text/markdown requests, which could be a natural follow-on feature. See Part 2 This is a quick win that puts eDirectory sites ahead of the vast majority of the web right now. The window where this is a differentiator rather than table stakes won't be open long. Aaron

Aaron B 3 months ago
Open AI Provider Settings — Custom API Endpoint + Model Name
I'd like to raise what I think is one of the most impactful feature improvements you could make to the AI section of eDirectory: opening up the AI provider configuration to allow a custom API base URL and model name, rather than locking users to just OpenAI. The OpenAI API standard is to AI what S3 is to object storage The best way to understand this is by analogy. Years ago, Amazon S3 defined an API standard for object storage. Today, dozens of providers — Cloudflare R2, Backblaze B2, Wasabi, MinIO, and many others — all implement that same S3-compatible API. The result is that any application built to talk to S3 can switch providers by simply changing an endpoint URL and credentials. No code changes. No re-integration work. The OpenAI /v1/chat/completions API has become exactly the same thing for AI inference. It is now the de facto industry standard protocol, and virtually every major AI provider in the world has adopted it as a drop-in compatible interface. Western providers OpenAI — api.openai.com/v1 Google Gemini — generativelanguage.googleapis.com/v1beta/openai xAI / Grok — api.x.ai/v1 Mistral AI — api.mistral.ai/v1 Groq — api.groq.com/openai/v1 Together AI — api.together.xyz/v1 Fireworks AI — api.fireworks.ai/inference/v1 Perplexity — api.perplexity.ai OpenRouter — openrouter.ai/api/v1 (routes to 100+ models via one key) Ollama (self-hosted) — localhost:11434/v1 LM Studio (self-hosted) — localhost:1234/v1 Chinese providers (all OpenAI-compatible) DeepSeek — api.deepseek.com/v1 Z.ai / GLM (Zhipu AI) — api.z.ai/api/openai/v1 Qwen / Alibaba — dashscope.aliyuncs.com/compatible-mode/v1 MiniMax — api.minimax.chat/v1 Moonshot / Kimi — api.moonshot.ai/v1 ByteDance / Doubao — ark.cn-beijing.volces.com/api/v3 Baidu / ERNIE — qianfan.baidubce.com/v2 StepFun — api.stepfun.com/v1 Xiaomi / MiMo — via OpenRouter Tencent Hunyuan — api.hunyuan.cloud.tencent.com/v1 They all speak the same protocol. If eDirectory simply exposed a custom API base URL and model name field, every single one of these becomes instantly usable — with zero additional development work on your end. One implementation unlocks the entire ecosystem, now and for every provider that emerges in the future. Just like S3 compatibility did for storage. The cost case

Aaron B 3 months ago
Open AI Provider Settings — Custom API Endpoint + Model Name
I'd like to raise what I think is one of the most impactful feature improvements you could make to the AI section of eDirectory: opening up the AI provider configuration to allow a custom API base URL and model name, rather than locking users to just OpenAI. The OpenAI API standard is to AI what S3 is to object storage The best way to understand this is by analogy. Years ago, Amazon S3 defined an API standard for object storage. Today, dozens of providers — Cloudflare R2, Backblaze B2, Wasabi, MinIO, and many others — all implement that same S3-compatible API. The result is that any application built to talk to S3 can switch providers by simply changing an endpoint URL and credentials. No code changes. No re-integration work. The OpenAI /v1/chat/completions API has become exactly the same thing for AI inference. It is now the de facto industry standard protocol, and virtually every major AI provider in the world has adopted it as a drop-in compatible interface. Western providers OpenAI — api.openai.com/v1 Google Gemini — generativelanguage.googleapis.com/v1beta/openai xAI / Grok — api.x.ai/v1 Mistral AI — api.mistral.ai/v1 Groq — api.groq.com/openai/v1 Together AI — api.together.xyz/v1 Fireworks AI — api.fireworks.ai/inference/v1 Perplexity — api.perplexity.ai OpenRouter — openrouter.ai/api/v1 (routes to 100+ models via one key) Ollama (self-hosted) — localhost:11434/v1 LM Studio (self-hosted) — localhost:1234/v1 Chinese providers (all OpenAI-compatible) DeepSeek — api.deepseek.com/v1 Z.ai / GLM (Zhipu AI) — api.z.ai/api/openai/v1 Qwen / Alibaba — dashscope.aliyuncs.com/compatible-mode/v1 MiniMax — api.minimax.chat/v1 Moonshot / Kimi — api.moonshot.ai/v1 ByteDance / Doubao — ark.cn-beijing.volces.com/api/v3 Baidu / ERNIE — qianfan.baidubce.com/v2 StepFun — api.stepfun.com/v1 Xiaomi / MiMo — via OpenRouter Tencent Hunyuan — api.hunyuan.cloud.tencent.com/v1 They all speak the same protocol. If eDirectory simply exposed a custom API base URL and model name field, every single one of these becomes instantly usable — with zero additional development work on your end. One implementation unlocks the entire ecosystem, now and for every provider that emerges in the future. Just like S3 compatibility did for storage. The cost case

Aaron B 3 months ago
Sitemgr must approve
This is a much needed and great feature however it is of little use if the sponsors or listing claimer has to pay upfront and then we have to do a manual refund if we are not excepting the listing. It really is an easy work around with stripe to have charges deducted only once approved. That will make this feature usable. Please fix this. Thank you

Els 3 months ago
Sitemgr must approve
This is a much needed and great feature however it is of little use if the sponsors or listing claimer has to pay upfront and then we have to do a manual refund if we are not excepting the listing. It really is an easy work around with stripe to have charges deducted only once approved. That will make this feature usable. Please fix this. Thank you

Els 3 months ago
Listing Template Prompts
It would be very beneficial if we could add prompts and/or examples in the long and short description blocks to ensure sponsors are giving good information for their listings

Els 3 months ago
Listing Template Prompts
It would be very beneficial if we could add prompts and/or examples in the long and short description blocks to ensure sponsors are giving good information for their listings

Els 3 months ago
UX and design consistency
The sponsor dashboard does not align with personalisation of fonts, colours etc Like this page for example very outdated look and can this not be editable to just display available plans? This then redirects the sponsor to the list with us page which is not good UX

Els 3 months ago
UX and design consistency
The sponsor dashboard does not align with personalisation of fonts, colours etc Like this page for example very outdated look and can this not be editable to just display available plans? This then redirects the sponsor to the list with us page which is not good UX

Els 3 months ago
Geração de Conteúdo
O eDirectory tem muitas ferramentas para um portal ou guia local e aproveitando a AI, acho muito interessante criar conteúdo com API da AI. Buscar eventos e notícias atuais e inserir no site, agregando conteúdo diário ao mesmo.

Agência BRQuality 4 months ago
Geração de Conteúdo
O eDirectory tem muitas ferramentas para um portal ou guia local e aproveitando a AI, acho muito interessante criar conteúdo com API da AI. Buscar eventos e notícias atuais e inserir no site, agregando conteúdo diário ao mesmo.

Agência BRQuality 4 months ago
Create a more robust Deals management system
Would like to request this functionality, the abilty to add Deals to Mobile Wallet. Also can Deals be tied to a user to have it marked as redeemed once it is used?

WheresThatDeal 4 months ago
Create a more robust Deals management system
Would like to request this functionality, the abilty to add Deals to Mobile Wallet. Also can Deals be tied to a user to have it marked as redeemed once it is used?

WheresThatDeal 4 months ago
Sizing of images
Can we use AI to right-size an image for the Card page? Users who set up a listing do not have the time nor the inclination to size an image. They post what they have available. On the detail page it usually looks good, but for the card page it is more than likely wrong-sized. It looks bad.

Gibraan Ali 4 months ago
Sizing of images
Can we use AI to right-size an image for the Card page? Users who set up a listing do not have the time nor the inclination to size an image. They post what they have available. On the detail page it usually looks good, but for the card page it is more than likely wrong-sized. It looks bad.

Gibraan Ali 4 months ago
Including website and social media clicks to summary report
Hi, It would be great to include website, social media etc, to the summary report so subscribers or sponsors can see what visitors are interested in and where to focus his activities it also shows how visitors actually acting in sponsors page Thanks

R. Harb 5 months ago
Including website and social media clicks to summary report
Hi, It would be great to include website, social media etc, to the summary report so subscribers or sponsors can see what visitors are interested in and where to focus his activities it also shows how visitors actually acting in sponsors page Thanks

R. Harb 5 months ago
Enhanced Category Widget Flexibility
I’d like to suggest an enhancement for the category widget. Currently, it only allows selecting first-level categories, and the main categories and they cannot be reorganized. It would be very useful if the widget could: Include second- or third-level subcategories so users can find popular areas faster. Allow reordering of categories and subcategories, giving admins control over display order to optimize user navigation and experience. This improvement would make the directory more flexible, easier to navigate, and allow highlighting of the most relevant subcategories for users, improving both discoverability and engagement.

Shay Williams 5 months ago
Enhanced Category Widget Flexibility
I’d like to suggest an enhancement for the category widget. Currently, it only allows selecting first-level categories, and the main categories and they cannot be reorganized. It would be very useful if the widget could: Include second- or third-level subcategories so users can find popular areas faster. Allow reordering of categories and subcategories, giving admins control over display order to optimize user navigation and experience. This improvement would make the directory more flexible, easier to navigate, and allow highlighting of the most relevant subcategories for users, improving both discoverability and engagement.

Shay Williams 5 months ago
Completed
Feedback for eDirectory UI/UX Improvements
I really appreciate the AI module—it looks modern, functional, and refreshed. However, much of the rest of the UI feels outdated. The gray outlines and neutral backgrounds on pages, particularly in the listing area, make it look old-fashioned. A white background option and less rigid styling would modernize the interface. The spacing between sections is minimal, forcing me to manually add headers or delete content just to create breathing room. Consistency in fonts, sizes, and bolding across titles, headers, and sections—like in the pricing section—needs improvement, as inconsistencies make the interface less polished. It would be great to have more flexible content-building modules, allowing one-, two-, or three-row layouts with text, images, buttons, and content blocks. Being able to see edits live while building would significantly improve the experience compared to the current save-and-preview workflow. Overall, a small visual refresh—modern colors, consistent typography, improved padding, and more flexible content blocks—would make a huge difference in usability and perception, complementing the AI features that already feel up-to-date.

Shay Williams 5 months ago
Completed
Feedback for eDirectory UI/UX Improvements
I really appreciate the AI module—it looks modern, functional, and refreshed. However, much of the rest of the UI feels outdated. The gray outlines and neutral backgrounds on pages, particularly in the listing area, make it look old-fashioned. A white background option and less rigid styling would modernize the interface. The spacing between sections is minimal, forcing me to manually add headers or delete content just to create breathing room. Consistency in fonts, sizes, and bolding across titles, headers, and sections—like in the pricing section—needs improvement, as inconsistencies make the interface less polished. It would be great to have more flexible content-building modules, allowing one-, two-, or three-row layouts with text, images, buttons, and content blocks. Being able to see edits live while building would significantly improve the experience compared to the current save-and-preview workflow. Overall, a small visual refresh—modern colors, consistent typography, improved padding, and more flexible content blocks—would make a huge difference in usability and perception, complementing the AI features that already feel up-to-date.

Shay Williams 5 months ago