Part 1 — Technical, SEO/AEO, performance and functional QA

Technical launch-readiness review and remediation of the Framer website, including:

• Responsive and interaction QA

• CMS and metadata validation

• Titles and meta descriptions

• Canonical URLs and hreflang

• HTML language configuration

• Heading hierarchy and semantic page structure

• Server-rendered and crawler-accessible content

• Internal linking

• Image alt text

• Open Graph metadata

• Metadata completeness across relevant templates

• robots.txt

• sitemap.xml

• Google and AI search crawler accessibility at website level

• llms.txt

• Clear llms.txt navigation to important public website content

• AEO/GEO content structure

• Clear entity and company information

• Clear product and service descriptions

• Pricing discoverability where commercially applicable

• Trust-page review for About, Contact, Privacy and other relevant company pages

• Consistent company naming and entity information across the website

• Links to authoritative company profiles where available

• Content hierarchy and answer-friendly page structure

• FAQ and question-based content opportunities where appropriate

• Performance and Core Web Vitals

• Five-language validation

• Final launch QA

URL mapping and redirects

URL migration is included as part of the technical launch scope.

The existing and new URL structures will be compared and changed or removed public URLs will be mapped to the most appropriate destination in the new Framer website.

Redirect implementation will use Framer-native permanent HTTP 308 redirects. These serve the same permanent-migration purpose as HTTP 301 redirects and do not change the underlying old-URL → new-URL mapping approach.

Localized URLs will be included where relevant.

Redirects will be tested as part of final launch QA.

Functional parity and integrations

Functional testing includes:

• HubSpot form submissions

• Required form-field behaviour

• UTM parameter pass-through and attribution behaviour

• Cookie-consent functionality

• Google Tag Manager loading and consent-dependent tag behaviour

• Relevant buttons, links and conversion flows

Phished will provide the required Google Tag Manager container ID and any necessary access or configuration information.

Cookie-consent testing covers the technical implementation and behaviour of the website. It does not constitute a separate legal or privacy-compliance assessment.

Part 2 — Structured data

Implementation and validation of Schema.org / JSON-LD, including where applicable:

• Organization

• WebSite

• WebPage

• BreadcrumbList

• Product / Service

• SoftwareApplication where appropriate for describing the Phished product

• BlogPosting

• Article / case-study markup

• FAQPage

• Offers / pricing information where applicable

• Organization sameAs entity links

• Organization contactPoint

• Organization address / PostalAddress

• Author and publisher relationships

The implementation includes a CMS/schema field map and validation using Schema Markup Validator and Google tools where applicable.

Structured data will be reviewed for entity consistency so search engines and AI systems can clearly understand:

• Who Phished is

• What Phished offers

• Which pages describe products and services

• Which content is editorial

• Who publishes the content

• How pages relate to one another

• Which external profiles represent the same company

Only structured data relevant to the public website and its discoverability is included.

Part 3 — Support, continuity and handover

During the project, I will be the main point of contact.

Standard working hours are Monday–Friday, 09:00–18:00 CET/CEST.

Target response times:

• Critical / launch blocking: within 2 working hours

• High priority: within 4 working hours

• Normal issues and questions: within 1 business day

Continuity

For an ongoing SLA, Allsite will maintain continuity during planned holidays, illness or exceptional workload peaks.

Planned holidays are normally limited to a maximum of seven consecutive days, approximately two to three times per year.

Where my availability would materially affect the agreed SLA, a senior coworker with an equivalent level of Framer and technical expertise will be introduced as the temporary point of contact and provided with the access required to support the website during that period.

I remain the primary point of contact outside these temporary coverage periods.

Post-launch support

After launch, support can work in two ways:

• Monthly retainer: suitable if there is a predictable amount of ongoing work. The monthly allocation would be defined once the expected workload is clearer.

• Estimate + time tracking: Phished sends a request, I provide an estimate, Phished approves it, and the actual implementation time is billed at €300/hour.

Continued work can include new pages, redesigns, CMS changes, SEO/AEO improvements, integrations and technical website development.

The handover will cover the Framer structure, CMS, metadata, localization, structured-data setup, llms.txt, crawler configuration, redirects and publishing workflow so the Phished team can manage normal content updates independently.

Part 4 — Exact copy parity

Copy-parity work is a separate time-based workstream and is not included in the €9,600 core optimization budget.

At Phished's request, one or multiple of the five language versions can be reviewed.

For each selected language, the visible copy of the new Framer website will be manually compared against the corresponding language version of the existing www.phished.io website and identified differences will be corrected.

The review applies to all regular website pages except blog posts and case studies.

It can include:

• Headlines

• Body copy

• Buttons

• Labels

• Navigation

• Forms

• FAQs

• Other visible website text

This is a content-parity check, not a translation service. Allsite is not responsible for translating content, proofreading translations or validating the linguistic accuracy of localized content.

The work only verifies whether the content published on the existing website in a selected language matches the corresponding content in the new Framer project.

Actual time will be logged and billed at €300/hour.

Any new copywriting or content creation outside parity correction will be estimated separately.

Part 5 — Breakpoint content synchronization

The Framer project will be reviewed across all relevant website pages to identify instances where content has been independently overridden or detached across Desktop, Laptop, Tablet or Phone breakpoints.

Where technically appropriate, components will be refactored so content is shared between breakpoints while allowing layouts and responsive presentation to remain breakpoint-specific.

Because the amount of work depends on how the existing Framer project has been constructed and how many breakpoint-specific overrides currently exist, this work cannot be reliably estimated upfront.

Actual time will therefore be logged and billed at €300/hour.

Any unusually large structural issue identified during the review will be communicated before significant additional work is undertaken.

Accessibility / WCAG 2.2 AA

The optimization scope includes the specific technical accessibility-related items listed elsewhere in this proposal, including semantic page structure, heading hierarchy and image alt text.

A formal WCAG 2.2 AA conformance audit, certification or full remediation is not included.

Achieving WCAG 2.2 AA may require broader design and component changes, including areas such as contrast, states, keyboard interaction, focus behaviour, component patterns and responsive design.

If formal WCAG 2.2 AA conformance is required, this should be reviewed and scoped as a separate workstream after completion of the current optimization project.