Fluixo.ai
EN
Tell us about your business
Open menu ☰

WHAT YOUR CUSTOMERS NEED TO FIND

Everything we check. And why it matters.

A complete website is a connected system. This is our delivery checklist for technical SEO, AI-search readability, conversion and reliable operation. Ecommerce and CMS checks apply when your project needs them.

176 checks · 16 areas
01

Business context & page plan

8 checks

Why it matters

Your pages answer real buying questions, with a clear next step and evidence that belongs to your business.

How we verify it

Review the business brief, page map and source material before drafting. Check each page for a distinct purpose.

Technical details

  • Offer + audience + market
  • Search intent / keyword map
  • Page map / no orphan pages
  • Brand palette / typography / logo
  • Source-backed claims
  • One page = one useful purpose
  • Primary CTA / next step
  • Conversion goal + measurement plan
03

Every page's metadata

10 checks

Why it matters

Search snippets and shared links describe the actual page. Different pages carry distinct titles and descriptions.

How we verify it

Read the served HTML, not only stored fields. Check uniqueness, missing values, heading structure and image URLs.

Technical details

  • <title> / unique + relevant
  • meta name='description' / unique
  • One H1 / H2-H3 hierarchy
  • rel='canonical' / self + query policy
  • meta robots / googlebot / X-Robots-Tag
  • Open Graph: title, description, URL, locale
  • og:image / dimensions / alt / HTTP 200
  • Twitter/X summary_large_image
  • charset / viewport / html lang
  • Google + Bing verification / preserved owners
04

A connected entity graph

12 checks

Why it matters

Structured data connects the business, site, pages and offers. Facts and prices match what a visitor can see.

How we verify it

Parse JSON-LD, resolve @id references, reject duplicate identities and compare schemas with visible copy and actual offers.

Technical details

  • JSON-LD / @context / @graph
  • Stable @id references
  • Organization / name / logo / contact
  • WebSite ↔ publisher
  • WebPage ↔ isPartOf ↔ about
  • Service + Offer / actual price + currency
  • BreadcrumbList / one per page
  • FAQPage / visible questions + answers
  • Product / Offer / stock / variants
  • CollectionPage / Article / VisualArtwork / author / dates
  • No fabricated AggregateRating / reviews
  • No duplicate Organization / WebSite nodes
05

Crawling, indexation & sitemaps

14 checks

Why it matters

Useful canonical pages can be discovered. Duplicate, private and utility surfaces do not pollute the search inventory.

How we verify it

Read robots, XML and page HTML through the public delivery path. Compare sitemap entries with actual routes and language availability.

Technical details

  • robots.txt / one Sitemap declaration
  • Search crawling / CDN + WAF policy
  • AI-search access / training policy
  • Staging noindex / private surfaces
  • Noindex: search / filters / cart / account
  • Sitemap index + children by type × language
  • No empty / redirect / noindex / noncanonical entries
  • Real lastmod or no lastmod
  • xhtml:link alternates + x-default
  • XML escaping / encoded URLs
  • 50,000 URLs / 50 MB hard limits
  • Atomic regeneration / public cache freshness
  • Search Console + Bing submission
  • IndexNow changed URLs / not Google indexing
06

Languages that really work

Where applicable
13 checks

Why it matters

A translated site includes navigation, forms and search metadata, with the visitor staying in their chosen language.

How we verify it

Finish the source content first. Test every active language's real pages, links, forms and reciprocal alternates before exposing it.

Technical details

  • Complete source language before translation
  • Source + active language registry
  • Language-specific slugs / URLs
  • hreflang reciprocal + self + x-default
  • Canonical per language / html lang
  • Localized title + description + OG locale
  • Menus / footer / CTA / form messages
  • ALT / FAQ / body / legal content
  • Commerce / currency / checkout / emails
  • No accidental English fallback
  • Source fingerprint / translate changed content
  • Completion + public render before activation
  • Hidden preview / active languages consistency
07

Content for search and AI answers

10 checks

Why it matters

Search engines and answer tools can identify what you sell, who it serves, where you work and why it is credible.

How we verify it

Review factual sources, readable page copy and the relationships between pages. Remove generic filler, unsupported results and competing page intent.

Technical details

  • Explicit business / service / audience facts
  • Answer-first sections / useful FAQs
  • Readable HTML text / not image-only content
  • Evidence / author / provenance where relevant
  • Related services / contextual internal links
  • Unique page purpose / no keyword cannibalisation
  • Natural copy / no keyword stuffing
  • No invented numbers / testimonials / outcomes
  • Editorial dates tied to real changes
  • Useful scale / no generic page multiplication
08

Images, identity & social sharing

12 checks

Why it matters

Images load efficiently, explain the content and preserve your identity across pages, browser tabs and shared links.

How we verify it

Check actual image responses, dimensions, descriptions, browser rendering and brand consistency. Preserve existing indexed image URLs.

Technical details

  • WebP / AVIF where appropriate
  • srcset + sizes / responsive resolution
  • width + height / reserved space
  • Hero discovery / fetchpriority / LCP
  • loading='lazy' below the fold
  • Meaningful ALT / decorative empty ALT
  • Own imagery / licensed source / honest illustrations
  • Logo / favicon / social card HTTP 200
  • site.webmanifest / icons / theme color
  • CDN + object storage / CORS / MIME
  • Private masters / public derivatives
  • Existing media URLs / redirect compatibility
09

Performance & accessibility

11 checks

Why it matters

Pages stay quick and usable on phones, slower networks and assistive technology.

How we verify it

Use desktop and mobile journeys plus three mobile Lighthouse runs per representative template. Our delivery targets use the median, not a single lucky run.

Technical details

  • Lighthouse Performance ≥95 / every run ≥90
  • Lighthouse SEO 100
  • Accessibility + Best Practices ≥95
  • LCP ≤2.5s / CLS ≤0.1 / TBT ≤200ms
  • Font subset / limited weights / compression
  • Script budget / no unnecessary requests
  • 44px targets / keyboard / visible focus
  • Label + error association / semantic controls
  • Contrast / readable type / reduced motion
  • 390px + 1440px / no horizontal overflow
  • Cache / compression / expiry / purge checks
10

Conversion, from offer to action

8 checks

Why it matters

People understand the offer, price and next step, then complete an enquiry or purchase without avoidable friction.

How we verify it

Follow the complete journey from each entry page on desktop and mobile. Test the buttons, conditional fields, totals and confirmation.

Technical details

  • Offer + price visible above the fold
  • One primary CTA / clear next action
  • Real projects / no fabricated proof
  • Objections / scope / FAQ before commitment
  • Progressive brief / only relevant fields
  • Transparent creation + language + annual costs
  • Useful error recovery / no lost answers
  • Real success / no false lead or payment event
11

Forms, delivery & lead handling

10 checks

Why it matters

A confirmation means a request was actually accepted. Your team receives enough context to respond properly.

How we verify it

Test validation, abuse controls, durable receipt and delivery separately. For live email, verify a received message and authentication headers.

Technical details

  • Server-side validation / field + body limits
  • Email + URL syntax / escaped rendering
  • Honeypot / rate limit / origin checks
  • Turnstile verified server-side when used
  • Consent / purpose / retention
  • Durable receipt / outbox / deduplication
  • Notification + customer acknowledgement
  • SPF / DKIM / DMARC + received inbox proof
  • Failure shown / no fake thanks page
  • Quote / follow-up / CRM context
12

Ecommerce: the whole purchase

Where applicable
17 checks

Why it matters

Catalogue, displayed price, payment and confirmation describe the same purchase, in the visitor's language and currency.

How we verify it

Exercise allowed product choices, cart, search, filters, checkout and payment outcomes. Verify the order, signed webhook, confirmation and customer email.

Technical details

  • Complete product copy + gallery + price
  • Allowed variants / availability / weight / dimensions
  • Search index per language / zero-result control
  • Filters really filter / pagination keeps filters
  • Displayed price ↔ schema ↔ merchant feed
  • Currency display ↔ checkout ↔ actual charge
  • Shipping countries / carriers / phone explanation / limits / costs / lead times
  • Tax / return / cancellation terms consistency
  • Guest checkout / account creation choices
  • Stripe + PayPal configuration where agreed
  • Success / failure / cancellation / 3DS flows
  • Signed webhooks / order state / refund handling
  • Confirmation only for successful paid order
  • Branded emails in customer language
  • Merchant Center / product feed / delivery / returns
  • Real promotion window / sale expiry / no fake ratings
  • Cart recovery only with appropriate consent
13

Measurement that can be verified

10 checks

Why it matters

You can tell which pages and actions bring enquiries and orders without counting failed actions as sales.

How we verify it

Keep configured, sent and received states separate. Confirm events in the provider report and compare paid orders with transaction IDs.

Technical details

  • Site-specific GA4 / Matomo / Clarity IDs
  • One emitter per provider / no duplicate events
  • Consent before optional tracking / revoke
  • CTA / brief start / receipt / outbound Aria
  • view_item / cart / checkout / purchase where relevant
  • No email / phone / message in analytics payload
  • Provider received proof / transaction_id
  • Readable reports / retained verification owners
  • Search Console domain + URL property
  • Bing verification / actual submitted sitemaps
14

Security, hosting & recovery

12 checks

Why it matters

The website can be updated, monitored and recovered, with sensitive access and private data kept out of public pages.

How we verify it

Check real headers, exposed paths, timers and resource limits. Restore a backup in isolation and test rollback before relying on it.

Technical details

  • HTTPS / HSTS / CSP / security headers
  • Private origin / firewall / safe public surface
  • Credentials outside Git / public assets / logs
  • Authenticated admin / protected login / WAF
  • Versioned releases / staging separated from production
  • CMS + extensions / pinned + reviewed updates
  • Scheduled tasks / timers actually running
  • Capacity / memory / disk / resource limits
  • Logs / health check / actionable monitoring
  • Encrypted off-site backup / retention
  • Isolated restore proof / rollback plan
  • security.txt / ads.txt / site.webmanifest / MIME / no leaks
15

CMS controls when applicable

Where applicable
10 checks

Why it matters

The platform's settings match the site's real behaviour, rather than looking correct only in an admin screen.

How we verify it

Check the stored configuration, live runtime and rendered pages together. Conditional controls are measured on the platform actually used.

Technical details

  • Timezone / one time source
  • Stable permalink structure / one site identity
  • Comments + pingbacks policy
  • One scheduler / cron pair
  • Wordfence / registered licence / scheduled scans where required
  • No inactive vulnerable extensions
  • Typed language / commerce / email settings
  • OPcache / PHP runtime / worker limits
  • Object cache / autoload / catalogue queries
  • No cross-brand / cross-site configuration leakage
16

Launch, ownership & maintenance

9 checks

Why it matters

You receive a website with a documented scope, working access and a way to keep it maintained.

How we verify it

Record the checked revision and handover details. Verify public routes after launch and compare them with the pre-redesign inventory.

Technical details

  • Written scope / revisions / schedule
  • Domain + hosting + ownership + access
  • Existing DNS / mail preserved
  • Public entry matrix / old links + media
  • No unverified launch checklist marked complete
  • Checked revision / deployment / rollback record
  • Operator guide / content update process
  • Annual maintenance / upgrades / agreed changes
  • Post-launch monitoring / organic + conversion baseline

Our commitment is the work and its checks. Search rankings, AI citations and sales depend on demand, competition and continued marketing.

Lighthouse targets are delivery criteria, not scores already measured for your future website.

Tell us about your business. We will handle the website.

Your activity, an existing site, references and catalogue: the brief asks the useful questions so we can propose a clear scope.

Tell us about your business