Begin with a business goal
“We need more traffic” starts a conversation but is not yet a success criterion. Identify priority products or services, customers you can serve and useful actions: orders, enquiries, bookings or quotation requests. The provider needs to understand the limitations of the offer as well as the website.
For example, enquiries for one specialist service may matter more than visits to general articles. This illustrative situation does not require choosing keywords in advance. It helps identify which pages to investigate and what outcomes to discuss. Preserve baseline data before changes begin so there is something meaningful to compare later.
What to ask in the first conversation
Ask how the team approaches a similar problem: how it selects pages, who implements changes and what it needs from your staff. A useful answer relates to the project and includes follow-up questions. A universal list of identical tasks for every website reveals little about the actual collaboration.
When a project example is presented, ask about its baseline, period and the team’s contribution. Growth may coincide with seasonality, a larger product range or an advertising campaign. Some client information can reasonably remain confidential. To assess the method, look for a clear connection between the goal, changes and measurement rather than a large number without context.
What an initial review should explain
The review should explain what limits the website and why the proposed tasks take priority. Not every automated warning calls for an immediate rebuild. Ask for an affected-page example, the consequence and a way to verify the fix. This turns a recommendation into a concrete task you can discuss with a developer.
Initially provide only the access necessary to review data, preferably read-only. Do not share one password covering all services. Implementation permissions are a separate decision based on specific tasks. Domains, analytics accounts and source materials should remain under your company’s control so the project does not depend on one person’s private account.
What to look for in the work plan
Each significant task needs a purpose, affected pages or templates, an owner and a verifiable deliverable. Instead of “improved content”, look for the information added, the customer need it addresses and where it was published. Instead of “technical fixes”, ask what changed and which related functions were checked.
Discuss approvals separately. Who supplies product information, approves copy and authorises catalogue changes? When will verification happen? Recommendations awaiting your developers should remain visible in the report. Otherwise a lack of progress can be discussed without knowing which actions were actually implemented.
How to read rankings and organic traffic
An individual rank check needs a query, search engine, region, date and relevant device type. Without these, two numbers may describe different conditions. Average position in a webmaster tool summarises a set of impressions; it should not be treated as one permanent rank experienced by every user.
Also examine the pages and query groups producing visits. Separate searches containing the company name from other searches, compare equivalent periods and consider seasonality. Our article on Search Console average position explains why that metric can change. A change in one metric does not identify its cause: first understand the underlying data and comparison conditions.
Connect the work with enquiries
First define an enquiry and record it correctly. A phone-link click, submitted form and confirmed order are different events. Review them separately, then assess quality: the right service, suitable region and a person who can be contacted. A larger number of recorded actions does not describe the entire outcome.
Mark changes to measurement during the comparison period. A newly configured event can increase reported enquiries even if customer behaviour has not changed. Do not automatically attribute that difference to SEO. A transparent report explains what was measured, where limitations remain and which observations are supported by data.
Agree how the collaboration will work
Agree meeting frequency, task format and approval procedures. Keep a history of completed pages, materials, technical decisions and checks. Major changes deserve a separate review of their impact on forms, catalogue functions and integrations. This makes project discussions more practical and easier to follow.
An owner can check whether the plan is understandable, the company controls its accounts and reporting is transparent. Independent technical advice can help assess disputed recommendations or changes. To start a conversation with General iT, share the website and describe the goal; we can discuss the baseline, scope and measurement approach.
Common questions
Should I choose a provider promising first place?
A promise does not replace a manageable plan. Providers control the quality of agreed work, not search algorithms or competitors. Ask for measurable objectives and clear verification conditions.
Can the work be evaluated after one month?
A month can show whether a stage was delivered properly. Conclusions about search performance require comparable data, enough observation and consideration of site changes. The period depends on the task; there is no universal growth date.
Are rankings or enquiries more important?
They answer different questions. Rankings and visits describe visibility; enquiries help assess business impact. Review the connection and measurement limits rather than replacing everything with one metric.
Sources and documentation
From understanding to action
Connect the decisions in one plan.
A focused check helps identify a cause. When changes involve structure, development, content and analytics, agree them together with priorities, ownership and verification.
Tell us about your website, priorities and the issue you have observed. We will discuss whether you need a focused stage or coordinated promotion and what the initial scope should include.
Discuss coordinated promotion