Skip to content
العربيةLet’s talk

Practical guide

SEO proposals in Jordan: compare the monthly scope before the fee

Compare monthly SEO proposals in Jordan by deliverables, implementation ownership, Arabic and English scope, reporting and exclusions before agreeing a fee.

Lava Solutions · · 5 minute read

Printed charts, glasses, pencils and a calculator arranged on a desk for analysis.
Illustrative stock photo. Photo: Cht Gsml / Unsplash.

A monthly SEO proposal is useful when you can tell what will be investigated, what will change on the website, who will do the work and how completion will be checked. For a business in Jordan, those decisions also need to reflect the actual service area and the languages customers use.

This is a scope-comparison guide, not a survey of Jordanian agency prices. It offers a practical way to compare proposals without inventing a standard monthly fee. References are official Google guidance reviewed on 17 November 2026; the worksheet and examples are editorial recommendations.

Give suppliers the same starting brief

List your main services, customer types, locations actually served, website platform, current languages and the action a visitor should take. Explain who can approve content and who can change templates, redirects and forms. Include known constraints, such as a planned redesign or a developer available only at agreed intervals.

Request an initial assessment with evidence and open questions. Google’s guidance on hiring an SEO recommends understanding the business, discussing the work involved and giving only read access to Search Console at the audit stage. Later implementation access should match the approved work and remain under your organisation’s control.

A supplier who has not reviewed the site may reasonably propose discovery first. Ask what that stage produces and which decisions it will resolve. A long list of tool warnings is less useful than a prioritised explanation of the problems that affect your pages and customers.

Separate recommendations from implemented changes

Two proposals can use the phrase “technical SEO” while offering different work. One might provide a report for your developer; another might include a tested template change. Put that difference in writing before comparing totals.

Work areaSpecify in the proposalEvidence of completion
Initial diagnosisPages reviewed, evidence, priorities and unresolved questionsA dated issue register with recommended next actions
Technical changesWho edits, tests, approves and releases each changeA change log and relevant checks on the released pages
Service-page contentBrief, factual input, writing, revisions and publication responsibilityApproved pages that answer the agreed buyer questions
Arabic and EnglishWhich pages need full counterparts and who reviews each languageReviewed language versions with working navigation
MeasurementBaseline, reporting scope and agreed enquiry definitionsComparable reports with limitations and next decisions
HandoverAccess, documentation and unfinished work at the end of the engagementAn accessible record of changes, assets and open items

For every row, identify the supplier’s deliverable and your own dependency. If an employee must approve technical descriptions, that is real project work. State what happens when approval or developer access is delayed, rather than silently counting unfinished work as a completed monthly service.

Make bilingual scope concrete

For an Arabic–English site, specify the pages, reviewer and publication route for both languages. Translation should preserve the service being offered, the intended customer and the next action. Decide who verifies names, terminology and contact details rather than treating an automatic translation as final approval.

Google’s multilingual-site guidance recommends separate URLs for language versions and explains language-alternate annotations. Ask whether the proposal covers those checks, language switching and the actual visible content. A translated menu alone does not complete an Arabic service page.

Keep the geographic scope honest. A company serving Amman and selected nearby areas should provide that information to the writer. Do not turn a list of city names into claims about offices, completed projects or services the business has not verified.

Agree what a monthly report must explain

Keep work completed, search visibility and business enquiries separate. A report should connect each delivered change to its purpose, show relevant observations and state what remains uncertain. Increasing impressions does not by itself establish more qualified enquiries or revenue.

The Search Console performance report provides clicks, impressions, click-through rate and average position, with dimensions such as query, page, country and device. Agree the date range, search type and filters so comparisons are understandable. Request the underlying view or export alongside commentary.

For enquiries, define a completed submission, a relevant sales enquiry and a qualified opportunity with the people who receive them. Specify who maintains the measurement and checks missing or duplicate records. Avoid treating a button click as proof that a conversation happened.

A fictional example: two proposals with different responsibilities

Imagine a fictional Amman maintenance company with Arabic and English service pages. Proposal A includes diagnosis and content briefs but leaves all development and publishing to the company. Proposal B includes implementing approved template fixes and publishing reviewed copy.

The buyer asks both suppliers to scope the same priority pages, language reviews and evidence checks. If the company has no available developer, Proposal A has an unresolved dependency. If its internal team already owns those tasks, Proposal B may duplicate work. The useful comparison is the complete delivery arrangement, not an assumed winner or an invented market price.

Review exclusions and methods before signing

Separate setup work, recurring work and optional additions. Ask whether development, photography, translation review, external tools, advertising and major redesigns are included. Record the change-request process and what documentation remains available when the engagement ends.

Ask how content topics and any link-related activity are selected. Google’s spam policies address links created to manipulate rankings and scaled pages produced primarily for ranking manipulation without user value. A quantity target alone is not an adequate explanation of the work.

Google’s hiring guidance also rejects guarantees of first-place rankings. Ask for measurable deliverables and reasoned forecasts with assumptions, not promises outside the supplier’s control. To discuss your brief, explore Lava’s SEO services, review related website work, or contact us with your site, languages and priority services. If enquiries feed a CRM, our customer follow-up guide helps define what happens after submission.

Sources & further reading

A useful next step

Bring one real workflow.

Share the process you want to improve, the systems involved and the decision you need to make.

Talk to Lava ↗