# Website Content Audits for Government & Public Sector ## Find the gaps in how official information reaches AI agents Tityra audits official content delivery for better Agent Experience (AX). Get documented findings and practical recommendations. - **CHECK THE OFFICIAL SOURCE:** See what a tested client receives from your website. - **KEEP THE PUBLIC CONTEXT:** Review eligibility, dates and instructions together. - **PLAN THE IMPROVEMENTS:** Give publishing and technical teams evidence to act on. ## Official information needs to reach the reader [Who it helps](/government-public-sector#government-audiences) When someone asks an AI assistant about a public service, its answer may depend on whether the retrieval tool can read the official page. Eligibility details added only by JavaScript may be missing from the initial response. Your team needs to know which information is available and where delivery needs attention. ### Ministries and departments Review the public pages that explain national or regional services, policy and administrative procedures. ### Local authorities Assess council and municipal websites covering local services, applications and public notices. ### Public agencies and institutions Examine programme information, public resources and guidance published by your institution. ### Digital and publishing teams Give IT, web development and content teams a shared view of issues in official information delivery. ## Start with the information people need [Use cases](/government-public-sector#government-use-cases) These are examples of how an agreed assessment can support public-sector publishing. Choose the services, page types and websites relevant to your institution. ### Government services Check whether a client can retrieve the eligibility requirements, application steps and required documents published for a service. ### Official guidance and regulations Investigate technical barriers to retrieving published guidance, including unclear document relationships, dates and links to the official source. ### Public programmes and announcements Examine how programme details, funding criteria, deadlines and updates are delivered. Keep a closing date connected to the programme it describes. ### Websites across institutions Agree a sample across separately authorised websites. Use the findings to distinguish a shared publishing-template issue from a correction needed on an individual page. ## Check access, structure and official context [What we review](/government-public-sector#government-scope) Different retrieval tools can receive or interpret a page differently. We assess the agreed pages and checks, documenting observed behaviour and the evidence behind each finding rather than assuming every AI system works in the same way. ### Content delivery Compare the initial HTML with the rendered page. Look for service instructions, eligibility details or deadlines that appear only after JavaScript runs or an interaction takes place. ### Discovery and metadata Review links, page metadata and structured data within the agreed checks. Identify missing or inconsistent signals that make official resources harder to discover or describe. ### Structure and accessibility signals Examine headings, content boundaries, lists, tables and links. Document markup and accessibility issues that can separate an instruction from the information needed to understand it. ### Dates, authority and scope Look for the responsible institution, relevant dates, eligibility conditions and links to supporting guidance. Flag missing or unclear context without interpreting the law or validating policy. ## Give each finding a clear next step [Inside the report](/government-public-sector#government-report) Review the affected pages, supporting evidence and recommended changes together. Use the report to prioritise work with the people responsible for the content and the website. ### Affected pages and priority See where an issue was found, its severity and the content included in the assessment. ### Recorded observations Review what was received or displayed under the recorded conditions. Distinguish the observed result from a possible effect on another retrieval tool. ### Practical recommendations Connect each finding to a content, template or delivery change your team can investigate. ### A basis for follow-up Keep the original evidence available when reviewing a change. Request a new audit when you need a subsequent assessment of the website. ## Organise institutions and websites separately [Your workspace](/government-public-sector#government-workspace) Give each institution its own organisation and each website its own project. Colleagues use their own accounts, with access governed by their membership and role in the relevant workspace. ### Create an account and organisation A designated colleague signs up and creates an organisation for the ministry, agency or institution. One account can manage multiple organisations, with a separate membership and role in each. ### Add websites as projects A member with project-creation permission creates a project for each website within the selected organisation. Each project has its own audit requests, subject to website authority, scope and any required credit approval. ### Review and follow up When a report is released, authorised colleagues can review findings, evidence and recommendations in the workspace. Record remediation progress and request a new audit after changes when appropriate. ### Support the next release. And the one after it Weekly monitoring automates In-Depth Audits for enabled projects on every workspace plan. Each run uses organisation credits against your approved page budget, up to 100 pages. Pause or resume projects individually. Weekly reports are delivered after the required checks and credit settlement. Subscription fees and audit credits are separate; Expert Review needs its own approved scope and credit budget. ## Your audit workspace [View the workspace on the website](/government-public-sector#government-workflow) Review the evidence behind each finding, discuss what to fix with your team and track progress across projects. ### Integrates with the tools you already use - GitHub - Jira - Slack ### Developer tools - [CLI](/cli) - [MCP](/docs/mcp) ## Choose your workspace [Workspace plans](/government-public-sector#government-options) [Compare Starter, Pro and Enterprise workspaces](https://tityra.com/#pricing). Read the current monthly and yearly prices in [pricing Markdown](https://tityra.com/pricing.md) or the [public plan catalogue](https://app.tityra.com/api/public/plans). All plans support unlimited organisations and projects. Starter includes two members, Pro includes 10, and Enterprise supports unlimited members. Pro includes 5 In-Depth Audits per month and Enterprise includes 20, each covering up to 100 pages. Workspace subscriptions include member capacity, features and monthly audit allowances. Pro is £59/month or £590/year for 5 monthly audits and Enterprise is £199/month or £1,990/year for 20 monthly audits, excluding VAT. Annual billing costs ten monthly payments, with audit allowances renewed each month. Unused monthly audits do not roll over, while purchased credits cost £1 including VAT and never expire. Existing billing agreements are preserved. Audit credits cost £1 including VAT. In-Depth Audit covers up to 100 pages using one included monthly audit or 19 credits (£19 including VAT), with included audits used first. Failed or cancelled audits release their reservation. Compare the workspace plans on [the Government & Public Sector page](/government-public-sector), then [create a Tityra account](https://app.tityra.com/signup) to request an audit from your project. Track your request and access your report in Tityra. A request does not automatically start an audit or take payment. We confirm the scope before work begins. ## Questions public-sector teams ask [Questions](/government-public-sector#government-questions) ### How can we start with a limited assessment? Choose an agreed sample of public pages, such as a service description, its eligibility guidance and application instructions. Create an account to request an audit or contact our team to discuss the scope. The person requesting it must be authorised to have the website assessed, and we confirm the scope before work begins. ### Will this make AI assistants give accurate answers? Tityra can identify and document problems in the content delivered by your website. It cannot control which sources a third-party AI system retrieves or how it uses them, so the audit cannot guarantee accurate answers, citations or search visibility. ### Does the audit certify accessibility or regulatory compliance? No. We review accessibility signals and other agreed content checks, with evidence and practical recommendations. This is not a full accessibility conformance assessment, a legal review, a security assessment or government certification. ### Can we manage several institutions and websites? Yes. An account can belong to multiple organisations, and each organisation can contain separate website projects within its plan limits. Access depends on the membership and permissions in each organisation and project. Membership of one institution does not give access to another. ### Can you assess restricted services or private records? Start with public information you are authorised to have reviewed. Contact us before proposing a restricted resource so we can agree what can be assessed. Do not submit passwords, private citizen records or other confidential information with an enquiry. ### What happens after our team makes a change? Record remediation progress alongside the finding and keep the original evidence available for comparison. You can request a new audit of the relevant website when a subsequent assessment is needed; the original report does not automatically verify a fix. - [What is Agent Experience?](/agent-experience) - [Privacy notice](/privacy) - [Website overview](/index.md) - [Contact Tityra](mailto:info@tityra.com)