Webority.Seo.Collector 0.11.3

Webority.Seo.AspNetCore

SEO for Webority Razor Pages websites, one way to do each thing:

• Index protection: X-Robots-Tag, robots meta and robots.txt, all off one answer, so they never disagree.
• One page registry: [SeoPage(...)] declares a page's title, description, section, type and dates once; the head, the sitemap, the JSON-LD and ISeoPageRegistry all read it.
• Generated files: /robots.txt (with a typed AI policy), /sitemap.xml (split into an index past 50,000 URLs, cached with ETag), /feed.xml (RSS) and /feed.atom (Atom) of the article pages, /llms.txt, an opt-in /llms-full.txt, the IndexNow key file and /.well-known/security.txt.
• Discovery files: /.well-known/* and a static /llms.txt with a one-hour cache.
• [RedirectFrom]: permanent redirects.
• One canonical host, on by default: in Production every other host goes to CanonicalBaseUrl, except the deploy probes (/_version.txt, /.well-known/_version.txt, /health, ACME challenges). A site that must answer on every host sets Seo:Site:RedirectToCanonicalHost to false.
• Typed robots rules: site defaults (index, follow, max-image-preview:large) and per-page overrides, in the meta and the header alike.
• <seo-head />: title (with a brand of its own if set), description, canonical, robots, per-page hreflang, pagination links, Open Graph (with article:tag and article:author) and Twitter tags. An error response writes no canonical and no hreflang.
• <json-ld />: the page's whole @id graph (Organization with an optional parent, WebSite, WebPage or ProfilePage, breadcrumb, Article or BlogPosting with Person authors and a reviewer, FAQ, a WebApplication on tool pages), plus typed schema.org classes modelled on Schema.NET. An error response writes none.

services.AddWeboritySeo();                       // binds and validates Seo:Site

app.UseWeboritySeo();                            // after UseForwardedHeaders, before static files and caching
app.UseEndpoints(e => { e.MapRazorPages(); e.MapWeboritySeoEndpoints(); });

@using Microsoft.AspNetCore.Http
@using Webority.Seo.AspNetCore
@addTagHelper *, Webority.Seo.AspNetCore
<head><seo-head /><json-ld /></head>

@page
@attribute [SeoPage(Title = "About Webority", Description = "Who we are and how we work.", Modified = "2026-09-30")]

[RedirectFrom("/about-us")]
public class AboutModel : PageModel
{
    public void OnGet() => HttpContext.Seo().Faq.Add("Where are you based?", "Gurugram, India.");
}

Every page with a fixed address carries [SeoPage] or [NoIndex]; startup names any that carries neither. Misconfiguration stops startup with a message naming the page or setting. A page still setting ViewData["Title"] throws in Development and is logged elsewhere.

Webority.Seo.Collector collects search performance into the product's own database. A nightly run calls the Google Search Console, Bing Webmaster Tools, PageSpeed Insights and Ahrefs Rank Tracker collectors, skips any that already succeeded for the day, and logs every run. The product owns its DbContext and its schedule.

Webority.Seo.Admin adds the SEO pages to a Razor Pages admin host: overview, queries, pages, Bing, Core Web Vitals, rankings and collection runs. It reads the Collector's tables and is secured by one authorization policy the host names.

Proprietary: for use within Webority Technologies products.