Begin with the business question
Perhaps enquiries are poorly matched to your services, important products are difficult to find or a redesign is approaching. Those situations need different investigations. A short initial brief can identify the issue, the pages involved and what evidence is already available.
An existing website is not automatically a rebuild project. Equally, publishing more articles is not automatically the answer to a technical access problem.
Agree responsibilities before access
Website ownership, account permissions, content approval and release authority should be clear before changes begin. Keep control of your domain and business accounts, and use invited access where the relevant platform supports it.
The proposal should distinguish advice from implementation and ongoing maintenance. That makes it easier to coordinate with an existing developer or whoever handles your website internally.
Know what the evidence can tell you
Search impressions, visits, contact interactions and completed sales describe different stages. An honest report does not turn the easiest number to collect into proof of the outcome you care about.
Where data is missing or volumes are small, the limitation should be visible. The next sensible step may be a measurement improvement, a narrower test or more time, rather than a confident claim.
Common questions
Which service should I start with?
Start with the problem rather than the service name. Share your website and the decision you need help with. An initial review can establish whether the priority is technical, editorial, local, commercial or design-related.
How long does SEO take?
There is no fixed timetable for a commercial outcome. Some changes can be checked immediately, while search systems and customer behaviour take longer to reflect them. The scope should define delivery dates and review points without promising a result by a particular date.
Can you guarantee first place or AI recommendations?
No. Freya cannot control search ordering, map coverage or the recommendations an AI system produces. Guarantees about those outcomes are not part of the offer.
Can you work with my existing website and developer?
Yes. The brief can focus on the current site and provide a prioritised work list for your developer. Implementation and verification responsibilities should be agreed so that recommendations do not get mistaken for completed changes.
Do I need Google Analytics before starting?
No. Available Search Console data, website checks and business records can still inform a review. Any measurement gaps are recorded. Adding analytics or other tracking is a separate decision with its own access and privacy considerations.
Will I have to share account passwords?
Personal account passwords should not be sent by email. Where supported, use invited user access with permissions appropriate to the task. Keep ownership of your domain, website and business profiles.
Is ongoing maintenance included with a website project?
Only where the agreed scope includes it. Hosting, updates, content changes and monitoring need clear responsibilities. A design project should not leave those decisions implicit.
How do I make an initial enquiry?
Email [email protected] with your website address, main services or products and the problem you would like to address. Leave out passwords and sensitive customer information.