Feature Requests

Enrich LocalBusiness JSON-LD With Actual Business Hours
Title: Include opens and closes values in auto-generated LocalBusiness schema Current behavior: SmartDirectoryAI correctly generates LocalBusiness JSON-LD from listing data, including business name, description, phone, email, address, images, and an openingHoursSpecification array when business hours are entered. However, the generated hours schema currently includes only the dayOfWeek values and omits the actual opening and closing times. Example of current output: { "@type": "OpeningHoursSpecification", "dayOfWeek": "Monday" } Expected behavior: When a listing has opening and closing times entered in the native Business Hours section, the generated schema should include those values: { "@type": "OpeningHoursSpecification", "dayOfWeek": "Monday", "opens": "06:00", "closes": "22:00" } For days with identical hours, grouping multiple days into one OpeningHoursSpecification object would also be acceptable. Why this matters: The visible listing page already shows the correct business hours, but the structured data does not expose those times to search engines and AI agents. This creates an incomplete schema record and may reduce the reliability of AI/search answers about when a business is open. Recommended implementation: Map the existing native Business Hours fields directly into the generated openingHoursSpecification, including: dayOfWeek opens closes handling for closed days handling for overnight hours, if supported omission of hours when no valid times are entered Important: This should enrich the existing auto-generated LocalBusiness schema rather than create a second duplicate LocalBusiness block.
0
Title Enable Server-Side Rendering (SSR) / Pre-rendering for Snapshots (Crucial for AEO & AI Crawlers)
Problem: Currently, directory snapshots serve a minimal initial HTML shell containing only a "Loading..." placeholder, relying on client-side JavaScript to render directory content and listings. While human browsers render this fine, AI search crawlers (Perplexity, SearchGPT, ClaudeBot, OpenAI) and search bots do not wait for client-side JavaScript execution. When crawling snapshot sites, bots see an empty page, preventing directory content and local listings from being indexed or recommended in Answer Engine Optimization (AEO). Impact on Directory Owners: The main value proposition for local businesses joining a directory is SEO and AEO visibility. Serving client-side rendered HTML undermines this core feature, as listings cannot be ingested by AI search engines. Requested Feature / Solution: Server-Side Rendering (SSR) or Static Pre-rendering: Provide pre-rendered HTML output on initial HTTP requests so crawlers receive full page content instantly. Initial Schema & Metadata Payload: Ensure JSON-LD Schema (ItemList, LocalBusiness, Organization) and Open Graph tags are present in the raw HTML before client-side hydration. Dynamic Rendering / Prerender Support: If full SSR is not feasible natively, provide built-in support or integration guidelines for dynamic rendering (e.g., via Prerender.io or Cloudflare Edge Workers) for bot traffic. Expected Result: Search crawlers and AI answer engines read full directory text, categories, and business structured data on the first request without executing JavaScript.
0
Load More