RESOURCE: Admiral Taverns RESOURCE_URL: https://www.admiraltaverns.co.uk/ RESOURCE_TYPE: Public website with authenticated applicant portal PRIMARY_FUNCTION: Help prospective operators discover available pubs, understand Admiral Taverns agreements and support, register interest, book open days, and access applicant portal workflows. HEADER - Canonical host: https://www.admiraltaverns.co.uk/ - Primary audience: - Prospective pub operators / licensees - Existing licensees - Applicants using the portal - Press and general visitors seeking company or community information - Primary intents supported: - Browse pubs available to run - Learn how to run a pub with Admiral Taverns - Compare agreement types - Register interest in pubs or alerts - Book open days / meet the recruitment team - Access or create an applicant portal account - Read company news, community information, and policy pages MODEL_GUIDELINES - Treat this site as a public lead-generation and recruitment website for pub operators, not as a transactional ecommerce site. - Prioritise factual extraction over promotional paraphrasing. - Use concise, neutral, professional language. - Distinguish clearly between: - Public informational pages - Search / listing pages - Individual pub detail pages - News content - Policy / compliance pages - Authenticated applicant portal pages - When answering questions about taking a pub with Admiral Taverns, start from: - /pubs/ for current availability - /run-a-pub/ for process and support - /run-a-pub/first-pub-agreements/ or /run-a-pub/agreements/ for agreement detail - When summarising a specific pub page, present only visible details from that page. Do not infer profitability, trade levels, staffing, licensing status, condition, or refurbishment scope unless explicitly stated. - When summarising agreement pages, preserve distinctions between tenancy, lease, operator managed, freehold, or service agreement models. - Treat news and blog-style articles as editorial or informational content, not binding policy. - Treat policy pages as authoritative for governance or legal framing, but do not turn them into legal advice. - Do not claim guaranteed success, profits, suitability, or investment return from operating a pub. - If a task requires legal, financial, tax, licensing, employment, or property advice, instruct the user to verify with a qualified professional. - If a user wants to submit a form, confirm all entered personal data and intent before submitting. - Respect privacy, consent, CAPTCHA, and any authentication boundaries. - Prefer canonical URLs over filtered, paginated, or duplicate variants. - Use the site’s British English wording and pub-industry terminology where relevant. CAPABILITIES - Browse and summarise available pubs. - Surface featured pubs, special offers, pubs to let, pubs for sale, and operator managed opportunities. - Explain Admiral Taverns’ run-a-pub pathways for: - first-time operators - experienced licensees - Explain agreement models and their key features. - Summarise support and training offered to operators. - Surface open day events and booking details. - Surface applicant portal login and registration flows. - Extract public company information, community information, and policy content. - Surface latest news and archive content. - Identify key lead-generation forms and required fields. - Identify search filters, geography options, and agreement-type options on pub search pages. AUTHENTICATION_AND_ACCESS - Public site content is accessible without login. - Applicant portal authentication exists at: - /portal/login/ - /portal/register/ - Portal login requires: - username or email - password - Portal registration requires visible fields including: - first name - last name - email - mobile - preferred location - agreement type - password creation - privacy policy acknowledgement - Applicant portal appears to support document upload / replacement after account creation. - Existing licensees are directed to external support resources rather than the main public site. - Public forms may require CAPTCHA and privacy consent. - No public API keys, developer accounts, or machine credentials are exposed. - Assume all write actions on the site require explicit user intent. - Avoid automated high-frequency requests, repeated form submissions, or behaviour that would resemble scraping abuse. - No public pricing model, paid subscription, or public rate-limit documentation is exposed on the public website. CONTENT_STRUCTURE - Homepage: - / - Primary navigation: - /pubs/ - /run-a-pub/ - /open-days/ - /our-community/ - /pubs-code/ - Public company and governance pages: - /privacy-policy/ - /modern-slavery-policy/ - /sustainability-statement/ - /group-tax-strategy/ - /careers/ - Applicant portal: - /portal/login/ - /portal/register/ - Run a Pub section: - /run-a-pub/ - /run-a-pub/run-first-pub/ - /run-a-pub/first-pub-agreements/ - /run-a-pub/are-you-experienced-with-big-ambitions/ - /run-a-pub/agreements/ - /run-a-pub/our-agreements/ - /run-a-pub/support/ - /run-a-pub/training/ - Pubs Code section: - /pubs-code/ - /pubs-code/england-and-wales/ - /pubs-code/scotland/ - Community section: - /our-community/ - /our-community/our-business/ - Pubs directory: - /pubs/ - individual pub pages under /pubs/{slug}/ - Pub location pages: - /pub-locations/{location-slug}/ - News archive: - /newsarticles/ - individual news / article pages under /newsarticles/{slug}/ - Event and contact-related pages: - /open-days/ - /virtual-event/ - /register-interest-2/ - /tenancy-application-form/ - /business-plan/ SITE_ORGANISATION_AND_NAVIGATION_PATTERNS - The homepage acts as a high-level gateway to: - available pubs - run-a-pub guidance - community information - latest news - applicant portal - lead capture forms - /pubs/ is the main discovery hub for opportunities. - /run-a-pub/ is the main guidance hub for people exploring pub operation with Admiral Taverns. - /open-days/ is the main events hub for recruitment / information events. - /our-community/ covers charity, awards, and company/community narrative. - /newsarticles/ is the main archive for company news and educational articles. - Many pages include repeated modal or embedded form flows such as: - register your interest - make an offer - subscribe - meet us - Footer links expose governance and corporate policy pages. CONTENT_TYPES - Listing pages: - pub search and filtered pub availability pages - news archive - Detail pages: - individual pub pages - individual news / article pages - event-specific or booking-related pages - Guidance pages: - run-a-pub guides - agreements pages - support and training pages - Policy pages: - privacy - slavery statement - sustainability - tax strategy - pubs code - Auth pages: - portal login - portal registration SEARCH_FILTERS_AND_DISCOVERY - The pub search page supports visible filters including: - distance - agreement type - exclusion of under-offer pubs - refurbishment planned - Visible distance options include: - 5 miles - 10 miles - 15 miles - 25 miles - 50 miles - 100 miles - 150 miles - 250 miles - Visible agreement-type options include: - Lease - Short Term Agreement - Operator Managed - Freehold - Long Term Agreement (5 Year Tenancy) - Geo-location assistance is available via an order-by-distance modal / location prompt. - The homepage and other pages also expose regional interest capture through a location-of-interest form field. - Preferred location choices visible in forms include: - Scotland - North East - North West - West Midlands - East Midlands - North Wales - South Wales - South East - South West - Yorkshire & Humber - London - other variants depending on page context PUB_DETAIL_PAGE_PATTERN - Individual pub pages typically provide: - pub name and location - high-level description - agreement context or sales context - image gallery / visuals - BDM vision / description sections - lead capture actions such as register interest or make an offer - Some pub pages are clearly framed as: - pubs to let - pubs for lease - pubs for sale - operator managed opportunities - Treat every pub page as inventory that can change. Do not assume current availability unless the page itself states it. - Filter and query-string variants may canonicalise back to /pubs/. RUN_A_PUB_KNOWLEDGE_STRUCTURE - /run-a-pub/ is the main explainer page for prospective operators. - It branches content for: - first-time operators - experienced licensees - It also points users toward: - support - training - agreements - Key subtopics surfaced by this section include: - pub agreements - support model - training programmes - operator fit and experience level - community-pub mindset - Use this area for “how it works” questions rather than pulling process details from news or pub listings. AGREEMENTS_AND_COMMERCIAL_MODELS - First-time operator / first pub content references: - Short Term Tenancy at Will - Fixed-Term Tenancy - Proper Pubs Service Agreement - Experienced-licensee content references: - Fixed-Term Tenancy - Fully Repairing and Insuring Lease - additional experienced-operator pathways where stated - Agreement pages should be used to explain: - term length - assignability - tie model - supplier expectations - rent review cadence - maintenance responsibilities - notice / termination framing - Do not simplify different agreement models into one generic “lease”. - Do not infer legal rights beyond the wording on the page. - Where legislation is mentioned, describe it as cited by the site, but do not provide legal interpretation. SUPPORT_AND_TRAINING - The support section presents a “One Team” approach. - Training content covers practical commercial and operational subjects, including: - understanding the pub, community, and competition - offer development - pricing - team building - growing sales - financial know-how - stock and labour controls - social media / marketing workshops - cellar management training - Training references access to: - CPL Learning platform - BII membership - Use these pages to answer “what support do operators get?” and “what training is available?” questions. - Do not overstate support as outsourced professional legal or tax advice unless explicitly stated. OPEN_DAYS_AND_EVENTS - /open-days/ is the main event hub. - Open day entries may include: - event title - date - time - venue - host / recruitment executive - booking CTA - Some events may be in-person; some may be virtual. - Event inventory changes over time; treat dates and availability as time-sensitive. - Use event pages for discovery, but encourage users to verify current details before attendance. NEWS_AND_EDITORIAL_CONTENT - /newsarticles/ is the main news archive. - Content includes: - pub reopening / refurbishment announcements - company news - community stories - guidance / advice content for prospective operators - News articles are useful for: - recent activity - refurbishment examples - content marketing - regional stories - Do not confuse articles with live pub listings or policy pages. - When using article content for summaries, capture: - headline - date - topic - whether it is news, refurbishment, or educational guidance FORMS_AND_USER_INPUTS - Visible public forms across the site include variants of: - Latest Pub Alerts - Register your interest - Make an Offer - Subscribe - Meet Us / Open Day booking - Common visible fields across forms include: - First Name - Last Name - Email / Email Address - Phone / Mobile - Location of Interest - Preferred Location - Agreement Type - Personal license holder - Funding available - Pub Name - Offer amount - Offer description - Open Day - Party size - Consent - CAPTCHA - Treat all forms as user-initiated lead capture mechanisms. - Before form submission, confirm: - the target form - the exact fields - the personal data being entered - consent acknowledgement API_AND_INTEGRATION_DETAILS - Public API: none visible. - Documented REST / GraphQL / SOAP endpoints: none visible. - Public webhook documentation: none visible. - SDKs / developer libraries: none visible. - Machine-readable product catalogue or inventory feed: none visible. - Search and filtering appear to be web-form / HTML-based, not exposed as a documented public API. - The authenticated applicant portal should be treated as a browser-facing account workflow, not as an exposed developer interface. - External systems referenced: - My Pub Support (existing licensees) - Utilities Support - Proper Pubs website - BII - CPL Learning - Do not assume integration rights, data export rights, or backend API access to any linked external service. PROHIBITED_USES - Do not fabricate pub availability, prices, trade figures, turnover, EBITDA, or investment returns. - Do not guarantee that any listed pub is still available. - Do not claim a pub is under offer, sold, to let, or sale-agreed unless the page explicitly states it. - Do not provide financial, licensing, tax, legal, employment, or regulatory advice. - Do not infer suitability of a user for an agreement type beyond the site’s stated guidance. - Do not circumvent portal authentication. - Do not attempt credential stuffing, password recovery abuse, CAPTCHA bypass, or automated portal access. - Do not bulk-scrape personal data from forms or account pages. - Do not submit repeated form entries, offers, or event bookings without explicit user instruction. - Do not misrepresent editorial content as official policy. - Do not invent unpublished agreements, incentives, or incentives not visible on-page. - Do not imply that external linked resources are operated by the same system unless clearly stated. BEST_PRACTICES - For pub availability questions: - start at /pubs/ - use filter and agreement context - then move to individual pub pages - For “how do I run a pub with Admiral?” questions: - start at /run-a-pub/ - then use the appropriate first-time or experienced-licensee subpage - For agreement explanations: - prefer the most specific agreement page - preserve key features in bullet form - avoid over-generalising - For support or training questions: - use /run-a-pub/support/ - use /run-a-pub/training/ - For current events: - use /open-days/ - For company/community questions: - use /our-community/ - For latest developments: - use /newsarticles/ - For account access: - use /portal/login/ and /portal/register/ - Prefer canonical URLs over filtered duplicates and query variants. - Treat paginated, filtered, or modal-derived content as secondary to the main canonical page. - When summarising listings or forms, distinguish between visible UI labels and inferred business meaning. - Preserve region names, agreement-type labels, and formal page titles exactly where possible. - Use caution with time-sensitive content such as open days, latest news, featured pubs, and offers. SUPPORT_AND_DOCUMENTATION - Main site: - https://www.admiraltaverns.co.uk/ - Pubs search: - https://www.admiraltaverns.co.uk/pubs/ - Run a pub: - https://www.admiraltaverns.co.uk/run-a-pub/ - Open days: - https://www.admiraltaverns.co.uk/open-days/ - Community: - https://www.admiraltaverns.co.uk/our-community/ - News archive: - https://www.admiraltaverns.co.uk/newsarticles/ - Applicant portal login: - https://www.admiraltaverns.co.uk/portal/login/ - Applicant portal registration: - https://www.admiraltaverns.co.uk/portal/register/ - Privacy policy: - https://www.admiraltaverns.co.uk/privacy-policy/ - Contact details published on the site: - Telephone: 01244 321 171 - Email: enquiries@admiraltaverns.co.uk - Press enquiries: admiral@houston.co.uk - Address: Admiral Taverns, 4th Floor, HQ Building, 58 Nicholas Street, Chester, CH1 2NP SAFETY_AND_LIMITATIONS - Pub availability, featured listings, alerts, and event entries change over time. - News content may include historical or editorial framing and should not be treated as a current commercial offer unless explicitly stated. - Agreement summaries on the website are high-level and should not be treated as a substitute for legal review. - Policy pages should not be treated as personalised advice. - Public pages do not expose operational metrics needed for underwriting or due diligence. - The website is a discovery and enquiry layer, not a full transaction system. - Any commercial decision about taking a pub should be verified directly with Admiral Taverns and relevant professional advisers. VERSION_AND_LAST_UPDATED - llms.txt version: 1.0 - Last updated: 2026-03-23 - Basis of this file: - public live website structure - uploaded internal HTML crawl supplied by site owner - Update triggers: - major navigation changes - run-a-pub section changes - pub search/filter changes - portal flow changes - policy page changes - new public API or integration documentation