# Website Content Audits for Financial Services & Insurance ## Connect financial products and insurance policies to their conditions Tityra audits finance and insurance content for better Agent Experience (AX). Get documented findings and practical recommendations. - **SEE WHAT IS DELIVERED:** Check the information a tested client receives. - **KEEP THE CONDITIONS CONNECTED:** Review fees, exclusions and supporting context. - **GIVE TEAMS A NEXT STEP:** Plan content and delivery work using the evidence. ## The conditions matter as much as the headline [Who it helps](/financial-services-insurance#finance-audiences) A product page may show its main benefit while fees, eligibility conditions or exclusions appear elsewhere. If a retrieval tool misses that supporting information, it receives an incomplete description. Review what your website delivers and whether the important conditions remain connected to the product they explain. ### Banks and lenders Review public product pages, fee information and application guidance alongside the conditions that explain who a service is for. ### Insurers and brokers Assess how policy summaries, exclusions and supporting documents are delivered across selected insurance pages. ### Fintech and payment providers Examine public pricing explanations, service information and help resources, with attention to the limits and requirements described on each page. ### Content and digital teams Give publishing, product and web development colleagues evidence of issues in the delivery and structure of financial information. ## Choose the information your customers need [Use cases](/financial-services-insurance#finance-use-cases) These examples describe possible assessment scopes. Start with representative public pages and agree which content and checks will answer your team's question. ### Product information and fees Review selected product pages with their published fee explanations and eligibility conditions. Investigate whether a client can retrieve the details needed to understand the description. ### Insurance policies and exclusions Examine how policy summaries connect to exclusions and supporting wording. Record delivery or structure issues that can separate a coverage statement from the conditions published alongside it. ### Disclosures and application guidance Assess the availability and context of public risk disclosures, application instructions and required-document lists. Check the relevant dates and document relationships within the agreed sample. ### Websites across brands Review a separately authorised sample across product lines or brands. Distinguish content that needs a local correction from a shared template or delivery issue affecting several pages. ## Review delivery, structure and product context [What we review](/financial-services-insurance#finance-scope) An audit examines the agreed pages and checks under recorded conditions. Findings describe what was observed, with supporting evidence and recommended changes, without assuming that every AI retrieval tool receives or interprets the same information. ### Content delivery Where included in the agreed checks, compare the initial HTML with the rendered page. Look for important terms or explanations that appear only after JavaScript runs or a visitor opens an interactive element. ### Discovery and metadata Review page links, metadata and structured data within the agreed scope. Identify missing or inconsistent signals that make product pages and their supporting resources harder to discover or describe. ### Semantic structure Examine headings, lists, tables and links, including relevant accessibility signals. Check whether labels and relationships preserve the meaning of fee tables, comparison content and application instructions. ### Conditions and document context Look for eligibility details, exclusions, dates and links to relevant documents. Flag missing or unclear context without validating rates, judging product suitability or interpreting financial regulations. ## Connect each finding to the work it needs [Inside the report](/financial-services-insurance#finance-report) Review the affected pages, evidence and recommendations in one report. Use the findings to decide which publishing or engineering changes your team should investigate first. ### Affected resources See the pages involved, the severity of each finding and the content included in the assessment. ### Supporting evidence Review the recorded response or page behaviour. Keep the observation distinct from a possible effect on another retrieval tool. ### Practical recommendations Identify content corrections, template investigations or changes to delivery, with the evidence available to the team carrying out the work. ### Follow-up assessment Keep the original findings available when reviewing a change. Request a new audit when a subsequent assessment of the website is needed. ## Keep websites and audit work organised [Your workspace](/financial-services-insurance#finance-workspace) Organise websites into projects within the relevant organisation. Colleagues use their own accounts, with access governed by their membership and permissions in each workspace. ### Set up your organisation Create an account and an organisation for your business. If you manage separate businesses, the same account can belong to multiple organisations, with a separate membership and role in each. ### Create website projects A member with project-creation permission creates a project for each website. Each project has its own audit requests, subject to website authority, the agreed scope and any required credit approval. ### Review and follow up Once a report is released, authorised colleagues can review findings, evidence and recommendations. Members with write access can record remediation progress, then 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](/financial-services-insurance#finance-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](/financial-services-insurance#finance-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 Financial Services & Insurance page](/financial-services-insurance), 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 financial services teams ask [Questions](/financial-services-insurance#finance-questions) ### What should we include in a first assessment? Choose an agreed sample of public product pages and the resources needed to understand them, such as fee information, eligibility conditions, exclusions or application guidance. Create an account to request an audit or contact our team to discuss the scope. You must be authorised to have the website assessed. ### Does the audit check regulatory compliance or product suitability? No. A website content audit examines the agreed delivery, structure and context checks. It does not provide financial advice, interpret regulations, certify compliance or assess whether a product is suitable for a particular customer. ### Do you verify rates, fees or coverage claims? The assessment can identify whether published information is available and how it is structured or connected to supporting context. It does not verify the commercial accuracy of a rate, calculate product costs, validate policy coverage or replace your product and legal review processes. ### Will this guarantee accurate AI answers about our products? No. The report documents observed website behaviour and content issues under the agreed checks. Tityra cannot control which sources another AI system retrieves or how it uses them, and cannot guarantee answers, citations or rankings. ### Can the audit include customer accounts or transaction data? Start with public information you are authorised to have reviewed. The website content audit is not an assessment of banking systems, payment processing or account security. Contact us before proposing restricted resources, and do not send credentials, account details or private customer records with an enquiry. ### How can teams follow up after making changes? Review the recommendations with the colleagues responsible for the content and website, then record remediation progress alongside the findings. Request a new audit when you need a subsequent assessment; recording a change does not automatically verify that it resolves the original issue. - [What is Agent Experience?](/agent-experience) - [Privacy notice](/privacy) - [Website overview](/index.md) - [Contact Tityra](mailto:info@tityra.com)