Website audit

Send four visitors through your website. See what they think.

Three real buyer types and one AI agent walk your site, page by page, and narrate the friction as they hit it — then score it and tell you what to fix first.

  • Takes about two minutes
  • No signup to see your score
  • Tests AI-agent readability
0.0/10

Report findings

Website audit

attekus.com

Built for the hardest buyer in the country, then unreachable by any of them

September 1, 2026
SaaS
Full
Visit the site
5.9
/ 10
Leaking
5.6
AI readability

Attekus sells to the most evidence-hungry buyer there is — a council procurement committee — and has built the hard parts for exactly that audience. ISO 27001:2022, PCI DSS 4.0 and ASD Essential Eight alignment are stated plainly. There is a published REST API, single sign-on through Entra ID and Okta, and a named integration for every ERP a council actually runs. The local-government page is one of the sharpest ICP pages this rubric has scored.

Then the site makes itself unreachable and unprovable. Every call to action on every page points at the same contact page, and no phone number, email address or postal address appears there or anywhere else on the site. Meanwhile the pricing page leads with “reduce manual administration by up to 77%” and the dozen council stories behind it contain almost no numbers at all. The page called “In practice” turns out to be three hypothetical scenarios.

What this site is

What they do
Enterprise venue booking, event management, ticketing and appointments software for councils, government agencies and universities across Australia and New Zealand, previously sold as Bookable.
Who it is for
Councils, government agencies and education providers across Australia and New Zealand. Their own words: “Built for councils. Proven in practice”, addressed to booking officers, venue and events managers, IT managers and directors of community services.
Sectors
Local government, State and federal government, Education, Commercial venues, Associations
What they sell
Venue and facility bookings, Event management, Event registration and ticketing, Appointments, Customer engagement, Payments, ERP and access-control integrations
Conversion event
Starting a “discovery” conversation via /contact/, which every call to action on every page points to; a support portal serves existing customers separately.
Proof on hand
18 named council and agency logos on the homepage, a dozen council stories on page one of /our-experience/ with a second page behind it, ISO 27001:2022, PCI DSS 4.0 and ASD Essential Eight alignment, a published REST API, named ERP and access-control integrations, a procurement resource written for council tender processes
Buyer facts found
Product category, Industries served, Security certifications, Named ERP integrations, Access-control integrations, SSO providers, REST API availability, Pricing model and what it scales on, Named council customers
Buyer facts missing
Any price, band or range, Implementation timeline, Contract or licence terms, Data residency, A phone number, An email address, A postal address, Any quantified customer outcome, Any named testimonial
Machine readability
Server-rendered — every page in this run returned full readable text without executing JavaScript. robots.txt is fully permissive (“User-agent: *” with an empty “Disallow:”) and declares the sitemap index. An llms.txt is published with 31 described URLs, which is rare and genuinely useful. Open Graph and Twitter Card tags present; no JSON-LD visible. No contact route of any kind is extractable.

A company that has done the difficult work for a difficult buyer and then left the front door locked. The security certifications, the published API and the named ERP integrations are exactly what a council IT manager needs, and he got all of it. The two buyers either side of him did not: one could not find out what it costs or who to ring, and the number the site leads with — a 77% reduction in manual administration — is supported by a dozen customer stories that between them contain one numeral. Fixing this is not a rebuild. It is a phone number, a set of results, and moving two links out of the footer.

The four visitors

Cold visitor

Nerida Cass

Booking officer, regional council in NSW

Awareness

Mixed

Arrived

Googled “council venue booking software” after a third double-booking this month.

Wants

To know in ten seconds whether this is built for councils or for commercial venues.

Judges on

Whether the first screen says what the product actually is, and whether councils like hers appear.

  • Lands on the homepage. Experience Starts Here. Powering communities through smarter connections. I have no idea what this company sells. (/)
  • Scrolls one section down. Attekus is enterprise-grade software for venue booking, event management, ticketing, and customer engagement. There it is. That sentence should be the headline. (/)
  • Reads the logo wall. Brisbane City Council, Sydney Olympic Park, City of Launceston, Randwick, Hume, Mornington Peninsula. Councils my size and councils ten times my size. (/)
  • Looks at the top navigation. By Industry, Talk to us, Support Portal. Three items. Where is everything else? (/)
  • Clicks See it in practice. Three real scenarios that show how Attekus works in practice. Then: Scenario 1, Scenario 2, Scenario 3. These are made up. I wanted customers. (/in-practice/)
  • Finally finds her own page. Built for councils. Proven in practice. This is the page I needed first, and it was two clicks and a footer away. (/local-government/)

Ready to act

Tom Beckwith

Coordinator community facilities, metro council

Consideration

Stalled

Arrived

Has budget this financial year and a manual process he wants gone. Straight to pricing.

Wants

An indicative cost, and a human to start the conversation with.

Judges on

Whether there is a number, and whether there is any way to reach anyone.

  • Goes straight to the pricing page. Predictable Investment, Measurable Impact. Good title. Now give me a number. (/solutions-pricing/)
  • Reads how pricing works. One annual SaaS fee. Unlimited bookings, no per-booking commission or transaction fees. Priced on rateable properties. That is the model explained honestly, and I still cannot budget it. (/solutions-pricing/)
  • Reads the headline claim. Reduce manual administration by up to 77%. That is a big number. Where did it come from? (/solutions-pricing/)
  • Goes looking for the 77%. A dozen council stories on page one. Broken Hill, Hornsby, Logan, Mosman, Whittlesea. Every one of them describes what was done and none of them says what it saved. (/our-experience/)
  • Clicks Start your discovery today. Get in touch. Our expertise your community. Warm words, and not a phone number in sight. (/contact/)
  • Looks for a phone number. No phone number. No email address. No street address. Not on this page, not in the footer, not anywhere I have been. (/contact/)
  • Goes back to the start. Every button on this site says Start your discovery today, and every one of them lands me on the same page with no one to call. (/)

Comparison shopper

Sandeep Rao

IT manager, council of 180,000 residents

Evaluation

Good

Arrived

Assessing Attekus against the booking module in the council's existing ERP.

Wants

Security posture, integration reality and API access, in enough detail to brief a security review.

Judges on

Named certifications, a real API, SSO, and whether the ERP integration is specific or hand-waved.

  • Opens the council page. Built for councils. Proven in practice. Community bookings, venue hire, events, ticketing and payments. That is my brief, back at me. (/local-government/)
  • Looks for the security posture. ISO 27001:2022, PCI DSS 4.0 and ASD Essential Eight alignment. Named, current, and the exact three my security review will ask for. (/local-government/)
  • Checks the ERP story. TechnologyOne with automated ETL posting, Civica, Datascape, ReadyTech, MAGIQ. Named systems, not logos. Someone has actually done these. (/integrations/)
  • Checks authentication. REST API published, single sign-on through Microsoft Entra ID and Okta, customer identity through Cognito. I can write the integration section of the brief from this page. (/integrations/)
  • Reads the council stories. Maribyrnong replaced fragmented booking processes across eleven different areas, live March 2022. Useful. But not one of these has a named person saying it. (/our-experience/)
  • Finds the procurement resource. Procurement Made Simpler, for councils navigating tender, contract and approval processes. They have met this buying process before. (/local-government/)
  • Writes his recommendation. Certifications named, API published, ERP integrations specific. On the technical criteria this clears the bar. Procurement will have to get the price by phone, if they can find one. (/local-government/)

AI agent

Procurement research agent

AI assistant acting for a council procurement officer

Task execution

Partly blocked

Arrived

Direct fetch. Task: shortlist ANZ council booking platforms with security certifications, TechnologyOne integration, indicative pricing and a contact route.

Wants

Certifications, integrations, a price and a non-form contact channel, all extractable as text.

Judges on

Readable without JavaScript · buyer facts extractable · structured data · non-form contact.

  • Checks crawl policy first. User-agent star, Disallow empty, sitemap index declared. Nothing is fenced off. I am fully welcome. (/robots.txt)
  • Finds a file written for it. An llms.txt with 31 URLs, each with a description of what the page is for. I understood this product range in one fetch instead of six. (/llms.txt)
  • Extracting fact 1 of 4 — price. Pricing is based on your organisation's size. No figure, no band, no range. Nothing to return. (/solutions-pricing/)
  • Extracting fact 2 of 4 — certifications. ISO 27001:2022, PCI DSS 4.0, ASD Essential Eight. Retrieved. High confidence. This is the part my user will care most about. (/local-government/)
  • Hits a contradiction. More than 130 councils across ANZ, and more than 120 councils, on the same page. Two values for one fact. Flagging rather than reporting either. (/local-government/)
  • Checks structured data. Open Graph and Twitter cards on every page. No JSON-LD I can see, so the product, the pricing model and the certifications are readable prose but not machine-stated facts. (/)
  • Extracting fact 3 of 4 — a contact route. No telephone, no email and no postal address on the page every call to action points at. I have nothing to hand my user. (/contact/)
  • Reports back to its user. Certifications and integrations retrieved with high confidence. Council count contradictory. Price unavailable. Contact route unavailable, so I cannot complete the task my user actually set. (/)

Journey feed

Cold visitor

Nerida Cass

/

lands on the homepage

Experience Starts Here. Powering communities through smarter connections. I have no idea what this company sells.

AI agent

Procurement research agent

/robots.txt

checks crawl policy first

User-agent star, Disallow empty, sitemap index declared. Nothing is fenced off. I am fully welcome.

Ready to act

Tom Beckwith

/solutions-pricing/

goes straight to the pricing page

Predictable Investment, Measurable Impact. Good title. Now give me a number.

AI agent

Procurement research agent

/llms.txt

finds a file written for it

An llms.txt with 31 URLs, each with a description of what the page is for. I understood this product range in one fetch instead of six.

Cold visitor

Nerida Cass

/

scrolls one section down

Attekus is enterprise-grade software for venue booking, event management, ticketing, and customer engagement. There it is. That sentence should be the headline.

Comparison shopper

Sandeep Rao

/local-government/

opens the council page

Built for councils. Proven in practice. Community bookings, venue hire, events, ticketing and payments. That is my brief, back at me.

Ready to act

Tom Beckwith

/solutions-pricing/

reads how pricing works

One annual SaaS fee. Unlimited bookings, no per-booking commission or transaction fees. Priced on rateable properties. That is the model explained honestly, and I still cannot budget it.

Cold visitor

Nerida Cass

/

reads the logo wall

Brisbane City Council, Sydney Olympic Park, City of Launceston, Randwick, Hume, Mornington Peninsula. Councils my size and councils ten times my size.

Comparison shopper

Sandeep Rao

/local-government/

looks for the security posture

ISO 27001:2022, PCI DSS 4.0 and ASD Essential Eight alignment. Named, current, and the exact three my security review will ask for.

AI agent

Procurement research agent

/solutions-pricing/

extracting fact 1 of 4 — price

Pricing is based on your organisation's size. No figure, no band, no range. Nothing to return.

Ready to act

Tom Beckwith

/solutions-pricing/

reads the headline claim

Reduce manual administration by up to 77%. That is a big number. Where did it come from?

Comparison shopper

Sandeep Rao

/integrations/

checks the ERP story

TechnologyOne with automated ETL posting, Civica, Datascape, ReadyTech, MAGIQ. Named systems, not logos. Someone has actually done these.

Cold visitor

Nerida Cass

/

looks at the top navigation

By Industry, Talk to us, Support Portal. Three items. Where is everything else?

AI agent

Procurement research agent

/local-government/

extracting fact 2 of 4 — certifications

ISO 27001:2022, PCI DSS 4.0, ASD Essential Eight. Retrieved. High confidence. This is the part my user will care most about.

Ready to act

Tom Beckwith

/our-experience/

goes looking for the 77%

A dozen council stories on page one. Broken Hill, Hornsby, Logan, Mosman, Whittlesea. Every one of them describes what was done and none of them says what it saved.

Comparison shopper

Sandeep Rao

/integrations/

checks authentication

REST API published, single sign-on through Microsoft Entra ID and Okta, customer identity through Cognito. I can write the integration section of the brief from this page.

AI agent

Procurement research agent

/local-government/

hits a contradiction

More than 130 councils across ANZ, and more than 120 councils, on the same page. Two values for one fact. Flagging rather than reporting either.

Cold visitor

Nerida Cass

/in-practice/

clicks See it in practice

Three real scenarios that show how Attekus works in practice. Then: Scenario 1, Scenario 2, Scenario 3. These are made up. I wanted customers.

Ready to act

Tom Beckwith

/contact/

clicks Start your discovery today

Get in touch. Our expertise your community. Warm words, and not a phone number in sight.

Comparison shopper

Sandeep Rao

/our-experience/

reads the council stories

Maribyrnong replaced fragmented booking processes across eleven different areas, live March 2022. Useful. But not one of these has a named person saying it.

AI agent

Procurement research agent

/

checks structured data

Open Graph and Twitter cards on every page. No JSON-LD I can see, so the product, the pricing model and the certifications are readable prose but not machine-stated facts.

Ready to act

Tom Beckwith

/contact/

looks for a phone number

No phone number. No email address. No street address. Not on this page, not in the footer, not anywhere I have been.

Comparison shopper

Sandeep Rao

/local-government/

finds the procurement resource

Procurement Made Simpler, for councils navigating tender, contract and approval processes. They have met this buying process before.

AI agent

Procurement research agent

/contact/

extracting fact 3 of 4 — a contact route

No telephone, no email and no postal address on the page every call to action points at. I have nothing to hand my user.

Cold visitor

Nerida Cass

/local-government/

finally finds her own page

Built for councils. Proven in practice. This is the page I needed first, and it was two clicks and a footer away.

Ready to act

Tom Beckwith

/

goes back to the start

Every button on this site says Start your discovery today, and every one of them lands me on the same page with no one to call.

Comparison shopper

Sandeep Rao

/local-government/

writes his recommendation

Certifications named, API published, ERP integrations specific. On the technical criteria this clears the bar. Procurement will have to get the price by phone, if they can find one.

AI agent

Procurement research agent

/

reports back to its user

Certifications and integrations retrieved with high confidence. Council count contradictory. Price unavailable. Contact route unavailable, so I cannot complete the task my user actually set.

How each score was reached

Nav Detail binds here.

Navigation & findability — 5.5 / 10

The top navigation is three items: “By Industry”, “Talk to us” and a support portal for existing customers. Everything a prospective buyer needs to evaluate — Solutions & Pricing, Our Experience, Integrations, Our Team, and the four pages written for the four roles on a buying committee — is reachable only from the footer. The IA underneath is well built and the sitemap is complete; it is the front door that is too narrow.

  • Top-level navigation: “By Industry”, “Talk to us” and “Support Portal” — three items, one of them for existing customers
  • /solutions-pricing/ and /our-experience/ are footer-only, so pricing and proof are both below the fold of every page
  • /it-managers/, /booking-officers/, /venue-events-managers/ and /director-of-community-customer-services/ exist in the sitemap and appear in no menu
  • “Sitemap: https://attekus.com/sitemap_index.xml” — declared in robots.txt, and it does index the real pages

Message clarity (ICP fit) — 7.5 / 10

The industry pages are excellent and the homepage hero is not. “Experience Starts Here” over “Powering communities through smarter connections” could introduce a telco, a consultancy or a charity; the sentence that actually explains the product sits one scroll below it, and it is a good one. Where this site is strong is the layer beneath: a council page written in council language, and four separate pages addressed to the specific roles on a buying committee. The deduction is for the first screen, and for a page called “In practice” that contains no practice.

  • “Experience Starts Here.” and “Powering communities through smarter connections” — the homepage hero, which does not name the product category
  • “Attekus is enterprise-grade software for venue booking, event management, ticketing, and customer engagement, designed for organisations where service delivery is complex.” — one section below, and the sentence the hero should be built from
  • “Built for councils. Proven in practice.” — /local-government/, which knows exactly who it is talking to
  • “Here are three real scenarios that show how Attekus works in practice.” — /in-practice/, followed by Scenario 1, Scenario 2 and Scenario 3, none of which is a customer

Trust & credibility — 7.0 / 10

For an enterprise government buyer this is mostly right. The three certifications a council security review actually asks about are named and current, the integration list is specific rather than a logo wall, and there is a resource written for the procurement process itself. Eighteen councils and agencies are named on the homepage alone. Two things pull it down: the site states two different council counts on the same page, which is the one number a procurement officer will quote back; and a company selling to government publishes no phone number, no email address and no postal address anywhere.

  • “ISO 27001:2022, PCI DSS 4.0 and ASD Essential Eight alignment” — /local-government/, named and current
  • “More than 130 councils across ANZ” and “more than 120 councils” — both on /local-government/
  • “Procurement Made Simpler” — a resource for councils navigating tender, contract and approval processes
  • No phone number, email address or postal address appears on any page reached in this run, including /contact/

Proof depth — 4.5 / 10

The weakest category, and the gap is specific rather than general: there is plenty of evidence that councils use this product and almost none of what it did for them. A dozen council stories sit on page one of /our-experience/ and exactly one contains a numeral. The detail pages behind them add operational colour but not outcomes. No named person is quoted anywhere on any page reached in this run. And the pricing page opens with a hard percentage that none of that evidence supports.

  • “reduce manual administration by up to 77%” — /solutions-pricing/, with no source, no customer and no case study attached to it
  • “Maribyrnong City Council — Consolidating venue bookings and events to improve the digital customer experience” — eleven hiring areas and a March 2022 go-live, and no stated result
  • Of the dozen council stories on page one of /our-experience/, one contains a numeral: a 140-day reference on the federal government story
  • No named testimonial with a speaker, title and organisation was found on any page in this run

Conversion path — 5.0 / 10

Every call to action on every page — “Connect with our team”, “Start your discovery today”, “Talk to us”, “Book here” — points at the same contact page. No phone number, email address or postal address appears on that page, or on any other page reviewed. A buyer who simply wants to ring and ask one question before committing to a discovery call has no way to do it, and there is no price, band or range anywhere to qualify the conversation against. Against that, the pricing page does something rare and good: it explains the commercial model in full without publishing a number.

  • “Start your discovery today” — the CTA on the homepage, the pricing page and the local-government page, all pointing to /contact/
  • “Get in touch” — the contact-page headline, on a page carrying no phone number, email address or postal address
  • “One annual SaaS fee” with “Unlimited bookings (no per-booking commission or transaction fees)” — /solutions-pricing/, the commercial model stated plainly
  • “Pricing is based on your organisation's size” — the same page, with no figure, band or range anywhere on it

Scored 5.6 out of 10. The working, so it can be checked:

  • Readable without JavaScript — 3 of 3. Every page in this run returned full text — navigation, headings, body copy, integration lists and certification names — without executing any of the site's JavaScript.
  • Buyer facts extractable — 1 of 3. Certifications, integrations, SSO providers, the API and the pricing model all came back cleanly as text. Two of the four facts the task depended on did not: there is no price, band or range anywhere on the site, and the council count is stated as both “more than 130” and “more than 120” on the same page, so an agent must report a contradiction instead of a value.
  • Structured data — 1 of 2. Open Graph and Twitter Card tags are present and well populated. No JSON-LD was visible, so the certifications, the integrations and the pricing model are readable prose rather than machine-stated facts. Treat this as worth confirming in the page source rather than proven — the site runs Yoast SEO, which often emits JSON-LD.
  • Non-form contact channel — 0 of 1. No telephone number, email address or postal address appears anywhere on this site, including the contact page that every call to action points at. There is nothing here an agent can hand back to its user.
  • Raw subtotal — 5 of 9, scaled to 5.6 of 10.
  • Crawl policy deduction — none, and then some. robots.txt is as open as it gets: “User-agent: *” with an empty “Disallow:” and the sitemap index declared. More than that, this site publishes an llms.txt — 31 URLs each with a written description of what the page is for. Publishing one at all is rare, and it is the reason the AI visitor understood the whole product range in a single read rather than crawling six pages for it. The rubric has no column for that, so it earns no points above; it deserves them.

Final: 5.6 of 10.

Report findings

Ranked by likely impact. Each finding quotes the page it came from.

Critical

Conversion path

Publish a phone number and an email address

“Connect with our team”, “Start your discovery today”, “Talk to us” and “Book here” all lead to the same contact page — and no phone number, email address or postal address appears on that page or on any other page reviewed. A council officer who wants to ring and ask one question before committing to a discovery call has no way to. For an AI assistant researching on a procurement officer's behalf, the task simply ends here with nothing to hand back.

Get in touch

View the page

What to do

  • Publish a phone number and an email address in the global footer, on every page
  • Add a postal address and the ABN — government buyers check the entity before they shortlist
  • Confirm the enquiry form on the contact page renders for every visitor, on desktop and on mobile
  • State a response time beside the enquiry form, the way the discovery process is already described
  • Add the phone number and email into llms.txt so assistants can retrieve them too

Critical

Proof depth

Evidence the 77% claim, or stop leading with it

The pricing page opens by promising to “reduce manual administration by up to 77%”. It is the single most persuasive number on the site and nothing anywhere supports it: no source, no customer, no methodology. Behind it sit a dozen council stories, of which exactly one contains a numeral. A council officer who goes looking for the evidence finds descriptions of work done and no statement of what any of it saved.

reduce manual administration by up to 77%

View the page

What to do

  • Name the customer, the measurement period and the method behind the 77%, next to the claim
  • Add a stated outcome to every council story: hours recovered, bookings processed, staff time redeployed
  • Where a result cannot be published, say which council it came from and why the figure is withheld
  • Retire the claim from the pricing page until at least three case studies support it

Serious

Trust & credibility

Settle on one council count

The local-government page states “More than 130 councils across ANZ” and “more than 120 councils”. It is the headline credibility claim of the whole business and it appears twice on one page with two different values. A procurement officer will quote whichever they read first, and an AI assistant asked to compare vendors has to report a contradiction instead of a number.

More than 130 councils across ANZ

View the page

What to do

  • Decide the correct figure and use it everywhere
  • Search the whole site, the capability statements and any tender collateral for the other value
  • Date the claim — “as at July 2026” — so it can be updated rather than quietly drifting
  • Consider stating the exact number instead of “more than”; a precise figure reads as counted rather than estimated

Serious

Navigation

Put pricing and proof in the top navigation

The top navigation is three items, one of which is a support portal for existing customers. Solutions & Pricing and Our Experience — the two pages a prospective buyer most wants — are reachable only from the footer. A booking officer who lands on the homepage has to scroll past the entire page to discover that a pricing page exists at all.

By Industry, Talk to us, Support Portal

View the page

What to do

  • Add Solutions & Pricing and Our Experience to the top-level navigation
  • Move the support portal to a smaller utility link so the main nav serves prospects
  • Keep By Industry as the first item — the industry pages are the strongest content on the site
  • Add a Resources or Company group so Integrations, Our Team and Our Story are reachable above the fold

Worth fixing

Message clarity

Promote the sentence that explains the product into the hero

“Experience Starts Here. Powering communities through smarter connections” could introduce a telco, a consultancy or a charity. One section below it is the sentence that does the job: enterprise-grade software for venue booking, event management, ticketing and customer engagement. A first-time visitor spends her first ten seconds not knowing what she is looking at, on a site whose deeper pages are unusually clear.

Experience Starts Here.

View the page

What to do

  • Lead with the category sentence and keep “Experience Starts Here” as the line above or below it
  • Name the audience in the hero — councils, government and education — as the local-government page already does
  • Test the hero against the ten-second question: does a stranger know what you sell and who for?

Worth fixing

Proof depth

Put a named person's words on the site

Not one named testimonial appears on any page reviewed — no speaker, no title, no council. For a buyer whose own reputation rides on the recommendation, a named peer saying it worked is worth more than another logo. The customers clearly exist; a dozen of them have written stories on the site already.

Trusted by councils across Australia and New Zealand

View the page

What to do

  • Get three attributed quotes with name, role and council, and put one on the local-government page
  • Add a quote to each customer story — the stories currently speak about the council, never as them
  • Ask for a short video from one reference customer; procurement committees watch them
  • Include the referee list you already use in tenders as a named logo strip with roles

Worth fixing

Message clarity

Rename “In practice”, or put real customers in it

The page promises “three real scenarios that show how Attekus works in practice” and then delivers Scenario 1, Scenario 2 and Scenario 3 — hypotheticals with no client, no name and no outcome. It is linked from the local-government page as “See it in practice”, so a buyer arrives expecting customers. The content is useful; the framing spends credibility the site cannot spare.

Here are three real scenarios that show how Attekus works in practice.

View the page

What to do

  • Drop the word “real”, or replace each scenario with the council that lived it
  • Rename the page to “How it works” and point “See it in practice” at the customer stories instead
  • Attach one named council to each of the three scenarios as a worked example

Worth fixing

Navigation

Surface the four role pages you already wrote

There are dedicated pages for IT managers, booking officers, venue and events managers, and directors of community and customer services. That is a buying committee mapped page by page, and none of the four appears in any menu — they exist only in the sitemap. Council software is bought by a group, and each member is currently one search away from the page written for them.

https://attekus.com/it-managers/

View the page

What to do

  • Add a “By Role” menu alongside “By Industry”, with all four pages
  • Cross-link the role pages from the industry pages — an IT manager arrives via local government
  • Put a role selector on the homepage so a visitor can self-identify in one click

Worth fixing

Trust & credibility

Repeat the security certifications where the technical buyer lands

ISO 27001:2022, PCI DSS 4.0 and ASD Essential Eight alignment are stated on the local-government page. The integrations page — where an IT manager evaluating the API and SSO actually spends their time — states no certifications at all, and no page reviewed states where data is hosted. For government buyers, data residency is a shortlisting question, not a detail.

Access Attekus Bookable data and services through our published Representational State Transfer (REST) API.

View the page

What to do

  • Repeat the three certifications on the integrations page and in the footer
  • State the data residency plainly — which country, which cloud region
  • Link the Trust Center from the integrations page, not only the footer
  • Publish the API documentation location, or say it is available under NDA

Worth checking

Machine readability

Reconcile llms.txt with the sitemap

The llms.txt lists customer-story URLs such as /maribyrnong-city-council and /redland-city-council. Those pages resolve, but neither appears in the page sitemap, so the two machine-readable indexes of this site disagree about what exists. The llms.txt also ends with a comment advertising the third-party tool that generated it, which will be read by every assistant that fetches the file.

<!-- Unlock the full power of AI on your site by creating a free AI customer service agent at https://sitespeak.ai -->

View the page

What to do

  • Add the customer-story pages to the sitemap, or remove them from llms.txt, so the two agree
  • Remove the vendor advertising comment from the end of the file
  • Regenerate llms.txt whenever pages are added, and put the check in the publishing routine
  • Add the phone number and email to llms.txt once they exist — it is the fastest way to give assistants a contact route

Keep doing

Conversion path

Keep explaining the pricing model even without a number

Most enterprise software sites say “contact us for pricing” and stop. This one explains what you are buying — one annual SaaS fee, unlimited bookings, no per-booking commission or transaction fees, scaled on rateable properties for councils and EFTS for education. A buyer can tell whether the commercial shape suits them before they ever speak to sales, which is most of what an indicative price is for.

One annual SaaS fee

View the page

What to do

  • Keep the model explanation exactly as it is
  • Add a band — “councils of 30,000 to 80,000 rateable properties typically invest between X and Y” — without committing to a quote
  • Say what a typical implementation costs on top of the annual fee, even as a range
  • Reuse the “no per-booking commission” line on the industry pages; it is a direct competitive hit

Keep doing

Machine readability

Keep the llms.txt, and keep it current

Publishing an llms.txt at all is rare — 31 URLs, each with a written description of what the page is for. The AI visitor understood the whole product range in a single read instead of crawling six pages, and arrived at the industry pages already knowing which one it needed. Paired with a robots.txt that disallows nothing, this site is materially easier for an answer engine to represent than most of its competitors.

- [Solutions & Pricing](https://attekus.com/solutions-pricing): Present transparent SaaS pricing and implementation details for community and government organizations.

View the page

What to do

  • Keep publishing it, and regenerate it whenever the page set changes
  • Write the descriptions by hand rather than leaving them generated — they are what an assistant quotes
  • Add the security certifications and the contact route into the file once published
  • Consider adding JSON-LD as well; llms.txt helps assistants navigate, schema helps them state facts

Send me a copy of this report

All findings with their tasks, the four visitor journeys and the methodology. We will email it within one business day.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Methodology and limitations

This audit puts four visitors through the site and reports what each of them found: a first-time visitor deciding whether it is for them, a buyer ready to act, a comparison shopper evaluating against alternatives, and an AI assistant researching on a buyer's behalf. It covers a content and structure review of eleven pages on the path to an enquiry — the homepage, local government, solutions and pricing, our experience, a customer story, in practice, integrations and contact, together with the robots.txt, the sitemap and the llms.txt — and scores five categories: navigation and findability, message clarity, trust and credibility, proof depth and conversion path. A separate AI-readability score measures how well an answer engine or AI assistant can read the site and extract the facts a buyer needs.

One caveat worth stating plainly: this is a UX and content review, not a page-speed or accessibility audit, and it does not include a rendered visual or mobile-layout assessment. For load performance, run the site through Google PageSpeed Insights.