# Ramfa SEO — expanded English public reference Generated from the same published content used by the main website. This is an optional reading reference, not a permission file or a ranking instruction. Each section links to its original page; Swedish and Persian versions are available from the source directory. ## A specialist-led practice, built around the work your website needs > Ramfa SEO is led by Ramin Amirhaeri in Gothenburg, Sweden. The practice brings technical SEO, website improvement, content strategy and measurement into one working relationship. You speak with the specialist responsible for understanding the problem and shaping the delivery. [Original page](https://ramfaseo.se/en/about/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Ramin Amirhaeri Ramfa SEO is led by Ramin Amirhaeri in Gothenburg, Sweden. The practice brings technical SEO, website improvement, content strategy and measurement into one working relationship. You speak with the specialist responsible for understanding the problem and shaping the delivery. A project can involve a small set of technical fixes, an e-commerce structure, a multilingual rollout or a longer programme of improvements. The starting point is the customer's search journey and the business decision behind the work. Scope, responsibilities and acceptance checks are made explicit. The project stories explain my role, the business problem and work that can be shared publicly. Client data and proprietary strategies stay private. My profile also links to professional experience and certificates. ### What I bring to a project - Technical audits and indexation - WordPress and WooCommerce - Next.js and JavaScript SEO - E-commerce architecture - Search intent and content strategy - Multilingual SEO - Core Web Vitals - Search Console and GA4 - Digital growth planning - AI search observation ### Based in Gothenburg. Working in Swedish, English and Persian. [LinkedIn](https://www.linkedin.com/in/ramin-amir-haeri/) ### Sources and language versions - [SV original](https://ramfaseo.se/om/) - [EN original](https://ramfaseo.se/en/about/) - [FA original](https://ramfaseo.se/fa/about/) --- ## Ramin Amirhaeri > SEO consultant, founder of Ramfa SEO and Digital Growth Manager. Based in Gothenburg, with work spanning technical search, e-commerce, WordPress and international websites. [Original page](https://ramfaseo.se/en/about/ramin-amirhaeri/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Ramin Amirhaeri My work sits between strategy and implementation. I investigate how a site is discovered and understood, how its content supports customer decisions and what needs to change in the platform or publishing process. I can work directly on agreed changes or alongside your developers and marketing team. I manage SEO and digital growth across MTC and its related projects, including Aptiva and Tezkar. My SEO management experience also includes Vedette Legal, Asacoin, Dubai Luxury Watch on Shopify, Building Material Dubai, Hostnegar and Misterkala. Each business needs a different approach. Product work includes Qotuno and the Ramfaseo internal team platform. I continue to develop my skills through professional learning in technical SEO, keyword strategy, local search, analytics and AI. The certificates below link to their original sources. Consultations are available in Swedish, English and Persian. ### What I bring to a project - Technical audits and indexation - WordPress and WooCommerce - Next.js and JavaScript SEO - E-commerce architecture - Search intent and content strategy - Multilingual SEO - Core Web Vitals - Search Console and GA4 - Digital growth planning - AI search observation ### Based in Gothenburg. Working in Swedish, English and Persian. [LinkedIn](https://www.linkedin.com/in/ramin-amir-haeri/) ### Sources and language versions - [SV original](https://ramfaseo.se/om/ramin-amirhaeri/) - [EN original](https://ramfaseo.se/en/about/ramin-amirhaeri/) - [FA original](https://ramfaseo.se/fa/about/ramin-amirhaeri/) --- ## Learning & earned certificates > Explore the courses and certificates behind my ongoing development in SEO, search strategy and applied AI. Each entry links to its source. [Original page](https://ramfaseo.se/en/about/credentials/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Learning & earned certificates Explore the courses and certificates behind my ongoing development in SEO, search strategy and applied AI. Each entry links to its source. - [Microsoft Azure AI Essentials Professional Certificate by Microsoft and LinkedIn](https://www.linkedin.com/learning/certificates/9487a42f6e13b0c69dde76f5eab51d617d966ddb28ffe56515722a250d329f71/): Microsoft & LinkedIn - [Get to Know Google Solutions for Google Partners Program - Data & Analytics](https://skillshop.credential.net/013fa0ad-1eae-4cff-a5c6-10942c8fa2eb): Google Skillshop - [SEO](https://app-eu1.hubspot.com/academy/achievements/km7kybkv/en/1/ramin-amir-haeri-khaledi/seo): HubSpot Academy - [Develop Your SEO Skills](https://www.linkedin.com/learning/certificates/7d0dacb87b9b3344a5fe889a038a218777a29da645bc3041af55e8f80c78670d/): LinkedIn Learning - [SEO Strategy: Link Building](https://www.linkedin.com/learning/certificates/9748a4a18d9cbdd9384d39da9f10eeeb92e126dbc27e79a8409e590f1a9b28fd/): LinkedIn Learning - [Marketing Tools: SEO](https://www.linkedin.com/learning/certificates/1ab1732e4b6767012eeade95820063c17b3f64fadde770bb2b8b60bc98579b12/): LinkedIn Learning - [SEO: Keyword Strategy](https://www.linkedin.com/learning/certificates/0304d677da2ee7e306a35ccdb3a7d1df19f0614f4bf24efc62682fffc61c6cd5/): LinkedIn Learning - [Learning Local SEO](https://www.linkedin.com/learning/certificates/7e0b550fa8e64e6785f227634c29f09036890de6983341f0e8267ec213425c9c/): LinkedIn Learning - [Technical SEO](https://www.linkedin.com/learning/certificates/8b19ea89fb369b6bad0b9b5ddd995ae1e4e65d24ea7f879fa092eae384453e59/): LinkedIn Learning - [SEO Foundations](https://www.linkedin.com/learning/certificates/dc36248fdf77a00724068288e5d6a57835d4ad0f61dacd032288993ec0733ab4/): LinkedIn Learning ### Sources and language versions - [SV original](https://ramfaseo.se/om/utbildningar-certifikat/) - [EN original](https://ramfaseo.se/en/about/credentials/) - [FA original](https://ramfaseo.se/fa/about/credentials/) --- ## Specialist depth, across the whole search journey > A technical issue rarely lives in isolation. Choose a focused service or combine the work into a plan for your business. [Original page](https://ramfaseo.se/en/services/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Choose the work your site actually needs You do not need to arrive with a diagnosis or buy every SEO service. Start with the decision you need to make. I can help you separate the immediate problem from the work that can wait. ### Where should you start? - [Important pages are missing from search](https://ramfaseo.se/en/services/technical-seo/): Check access, indexing and page templates before commissioning more content. - [You are changing a site, platform or domain](https://ramfaseo.se/en/services/wordpress-seo-migration/): Plan the migration before launch, while URLs and redirects can still be tested. - [You are adding or repairing language versions](https://ramfaseo.se/en/services/multilingual-seo/): Agree on which pages each audience needs, then connect equivalent versions. - [Products are visible but customers struggle to find the right range](https://ramfaseo.se/en/services/ecommerce-seo/): Start with categories, filters and product information, not a rewrite of every URL. - [Visitors still cannot decide whether your service fits](https://ramfaseo.se/en/services/content-strategy/): Work on questions, proof and the next step on the pages that support a buying decision. - [Pages feel slow or difficult to use](https://ramfaseo.se/en/services/website-performance/): Identify the slow templates and interactions before replacing the whole site. - [Search answers describe your business poorly](https://ramfaseo.se/en/services/ai-search-visibility/): Check the underlying pages, identity and evidence before adding special files or tools. - [There are too many possible fixes and no clear owner](https://ramfaseo.se/en/services/seo-consulting/): Build a short, ordered plan around business priorities and the team's capacity. ### An audit, implementation or ongoing support? These are ways to organise the work, not fixed packages. A small site can need a difficult repair; a large site may need one well-defined change. #### A focused review Choose this when the cause is unclear or you need a second opinion before committing development time. The useful handover is an explanation of the problem, evidence, priorities and a brief someone can implement. Agree separately whether fixes are included. #### A defined implementation project Choose this when the problem and intended change are clear, such as a migration, a set of templates or a group of service pages. Scope the pages or templates, responsibilities, release dependencies and checks for accepting the work. Any work outside that scope needs a separate decision. #### Ongoing SEO support Choose this when releases, products or content change regularly and someone needs to keep priorities aligned. Agree on the review rhythm, work capacity and reporting before starting. Ongoing support is not a promise to deliver every possible task each month. ### What determines the quote? A domain name alone is not enough to estimate the work. These details help turn a general request into a useful scope and price. #### The part of the site that needs work Templates, catalogue structure, language versions and integrations matter as much as the number of pages. #### Who will implement the changes Advice for your own developer and implementation by me involve different work. Content entry, design and specialist development should be explicitly included or excluded. #### The starting point and dependencies A usable test environment, existing research, access to reports and an approaching release can change the sequence and effort. ### Before approving the work, make sure this is clear - The problem we are addressing, the pages or templates in scope and the business outcome we will evaluate. - The deliverables, exclusions and who provides content, development, access and approvals. - The fee, currency, applicable taxes, payment terms and how a requested change to scope will be priced. - The planned milestones, dependencies and checks for accepting the delivered work. - The handover format, ownership of accounts and files, and whether support after delivery is included. ### What to send with your first message - Your public site address and two or three pages that illustrate the issue. - What visitors should be able to do, and what is currently getting in the way. - Your platform, language versions and any recent or planned migration or redesign. - Who can make changes, any real deadline and a budget range if you already have one. Please do not send passwords, customer records or private screenshots through the enquiry form. If access is needed later, we can agree on the minimum permissions for the task. Sending an enquiry does not place an order or start paid work. It gives us a starting point to discuss the scope. ### Questions before you commit #### Can I start with one problem instead of a monthly contract? Yes. A specific indexing issue, migration decision or page group can be scoped on its own. If other problems appear, we can distinguish what is necessary now from optional follow-up work. #### Can my developer or content team do the implementation? Yes. Tell me who will make the changes. We can scope the work around investigation, implementation instructions and review. Implementation by me should be explicitly agreed, not assumed from the word audit. #### When should I expect results? Agree on delivery milestones separately from search results. A redirect or a page change can be checked when released; crawling, indexing and customer response take their own course. The starting position and dependencies determine a sensible evaluation period. #### How do I compare two SEO proposals? Compare the problem being solved, pages or templates covered, actual deliverables, implementation responsibility and acceptance checks. Two proposals with the same service name can cover very different work. Ask what is excluded and how you will use the output. #### Do I need to buy an AI visibility service separately? Not automatically. If important pages are inaccessible, unclear or unsupported by evidence, fixing those fundamentals comes first. A separate engagement makes sense when there is a defined question about how your business is represented and a reproducible way to examine it. #### Can you guarantee rankings, sales or citations in AI answers? No. Those outcomes depend on systems and decisions outside the work itself. We can agree on concrete changes, verification and a way to evaluate progress without treating a forecast as a guarantee. ### Sources and language versions - [SV original](https://ramfaseo.se/tjanster/) - [EN original](https://ramfaseo.se/en/services/) - [FA original](https://ramfaseo.se/fa/services/) --- ## Find the technical barriers between your pages and search. > Important pages missing from Google? Conflicting canonical tags? A JavaScript website that looks fine to visitors but renders differently for search engines? I trace the problem from the affected URLs to the template, configuration or publishing process behind it. [Original page](https://ramfaseo.se/en/services/technical-seo/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Who this is for For marketing and development teams that need to understand why organic search is underperforming, or want a technical review before a redesign. The work covers WordPress, WooCommerce, Shopify and custom websites, including Next.js. ### What we work on - Discovery and indexation: robots rules, XML sitemaps, status codes, canonical selection and Search Console evidence. - Rendered content: compare the initial HTML and browser output, including navigation, metadata and JavaScript dependencies. - Architecture: category depth, internal links, pagination, duplicate URLs and parameter combinations. - Implementation risk: affected templates, development ownership, release order and checks that prove a fix worked. ### What you receive - A prioritized issue register with example URLs, business relevance and a clear next action. - Implementation specifications for your developers, or agreed fixes carried out directly. - Before-and-after technical checks and a follow-up plan for indexation and search performance. ### Planning the scope An audit is scoped to your site and available data. Search engine processing and rankings cannot be scheduled or guaranteed; technical acceptance and commercial outcomes are measured separately. ### Planning this service for your site #### A sensible starting point If the cause is unknown, start with a focused investigation of affected page types. If the issue is already confirmed, scope the fix and its verification instead of repeating a full audit. #### What to prepare Share example URLs, when the problem appeared, recent releases and any available Search Console reports. Read-only access may be enough for investigation; it does not require permission to change the site. #### What changes the scope Rendering, server rules, template variation and developer availability affect the work. A crawl report alone does not include implementing every issue it finds. #### How to review the handover Each priority should identify affected pages, evidence, an action and a way to check it. For implemented fixes, compare the agreed technical checks before and after release; an indexing request is not proof of indexing. ### A clear way to move from diagnosis to delivery #### Understand We review the website, your commercial priorities and the decision you need to make. #### Define You receive a scope with priorities, responsibilities and concrete deliverables. #### Implement I work directly on agreed changes or collaborate with your development and content teams. #### Verify We check the implementation and agree how to follow search and business outcomes. ### Questions worth asking before you choose an SEO partner #### Can you implement the fixes as well as audit the website? Yes. We can agree an audit, implementation or a combined engagement. Each change has an owner and an acceptance check, so the report does not become an unassigned task list. #### Do you work with Next.js and JavaScript websites? Yes. I investigate server-rendered content, client-side dependencies, routing, metadata, status codes and the links available to crawlers. Recommendations reflect how your application is actually built. #### Why are some pages crawled but not indexed? That status describes an outcome, not a single diagnosis. I compare the affected pages with indexed examples and inspect duplication, canonical signals, content usefulness, internal links and rendering. #### What access is useful? The site address and a description of the problem are enough for the first conversation. Search Console, analytics and a staging environment may be requested later with access limited to the agreed work. #### What should an actionable audit contain? Specific affected URLs, evidence, priority, a proposed correction, an implementation owner and a way to verify the result. A long export of tool warnings is not the deliverable. ### How to choose a service and plan the work [Choose the work your site actually needs](https://ramfaseo.se/en/services/) ### Sources and language versions - [SV original](https://ramfaseo.se/tjanster/teknisk-seo/) - [EN original](https://ramfaseo.se/en/services/technical-seo/) - [FA original](https://ramfaseo.se/fa/services/technical-seo/) --- ## Change your website with a plan for what search must keep. > A new theme, domain or platform changes more than the design. I connect the old site's valuable pages, content and search signals to the new structure, then test the journey from a search result to an enquiry or product. [Original page](https://ramfaseo.se/en/services/wordpress-seo-migration/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Who this is for For WordPress and WooCommerce businesses planning a redesign, changing URL structures or moving between platforms. Also suitable when plugin conflicts, templates or slow pages are holding an existing site back. ### What we work on - Inventory the pages, media, search landing pages and templates that need to be retained or intentionally replaced. - Map old URLs to useful new destinations and test redirects, loops, chains and missing pages. - Review titles, canonical tags, language relationships, internal links, forms and measurement before launch. - Coordinate release, verification and a practical return path with your hosting or development team. ### What you receive - An old-to-new URL map with a decision for each important page. - A pre-launch checklist and tested fixes for agreed WordPress, template or plugin issues. - A release sequence, recovery plan and post-launch checks for critical journeys. ### Planning the scope Content entry, payment integrations and a complete new store are scoped separately. Migration planning reduces avoidable errors but cannot promise zero traffic fluctuation. ### Planning this service for your site #### A sensible starting point Start before a migration or redesign goes live. For an existing broken site, first separate urgent recovery work from improvements that can follow. #### What to prepare Bring the current site, the proposed destination, important page types and the intended launch date. Identify who manages hosting, plugins, content and deployment. #### What changes the scope Changing a theme is different from changing URL structure, domain or CMS. Plugin compatibility, custom templates, shop functions and content transfer need explicit scope. #### How to review the handover Check representative old URLs, their final destinations, canonical tags and indexability. Test important forms and purchase paths too. Keep the redirect map and release decisions usable by whoever maintains the site. ### A clear way to move from diagnosis to delivery #### Understand We review the website, your commercial priorities and the decision you need to make. #### Define You receive a scope with priorities, responsibilities and concrete deliverables. #### Implement I work directly on agreed changes or collaborate with your development and content teams. #### Verify We check the implementation and agree how to follow search and business outcomes. ### Questions worth asking before you choose an SEO partner #### Should SEO be involved before the new design is built? Yes. Navigation, URLs, templates and content requirements are easier to plan before development. An early inventory prevents important search landing pages being lost during a visual redesign. #### Can I change platform and domain together? It is possible, but combining changes makes diagnosis harder. I review the dependencies and help decide whether a staged release or a single coordinated move is more appropriate. #### Do you replace every plugin? No. Existing tools are assessed by what they do, their dependencies and the problem they cause. Unnecessary replacements add risk and maintenance work. #### What happens to old URLs? Important old URLs receive a documented decision: retain, redirect to a relevant equivalent or return the appropriate removal status. Redirecting everything to the homepage is not a useful migration map. #### Can you work with my current developer? Yes. I can own the SEO requirements and verification while your developer implements them, or take on agreed technical changes directly. ### How to choose a service and plan the work [Choose the work your site actually needs](https://ramfaseo.se/en/services/) ### Sources and language versions - [SV original](https://ramfaseo.se/tjanster/wordpress-seo-migrering/) - [EN original](https://ramfaseo.se/en/services/wordpress-seo-migration/) - [FA original](https://ramfaseo.se/fa/services/wordpress-seo-migration/) --- ## Make every language version useful to its own audience. > A translated page is only one part of an international website. I work on the relationship between language versions, the content people need in each market and the path that takes them from a search result to the right service. [Original page](https://ramfaseo.se/en/services/multilingual-seo/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Who this is for For businesses serving more than one language, expanding into a new market or seeing the wrong language appear in search. Consultations are available in Swedish, English and Persian. ### What we work on - Map language and market goals to real equivalent pages and a sustainable URL structure. - Validate self-canonical URLs, reciprocal hreflang, x-default and sitemap consistency. - Review language switching, local terminology, service relevance and contact paths. - Check Persian RTL layouts, readable mixed-script text and mobile forms alongside the other languages. ### What you receive - A translation and URL registry that explains which pages belong together. - A market-aware content brief and priorities for missing or weak pages. - Technical corrections and repeatable checks for language relationships. ### Planning the scope Professional translation volume and market research are agreed explicitly. New language pages are published when they are useful and complete; hreflang is not a substitute for localized content. ### Planning this service for your site #### A sensible starting point Start with the pages each audience needs and which versions are genuinely equivalent. Translating every page is not a prerequisite for a useful first release. #### What to prepare List languages, existing URLs, planned pages and who can review each language. Include differences in the offer, contact process or product availability. #### What changes the scope The number of page templates, local writing, translation review and CMS language setup all affect the scope. Hreflang repair and writing a new language version are different tasks. #### How to review the handover Review a page-to-page language map, reciprocal language references, canonical consistency and language switching. Read the actual offer in each language: technical links cannot fix a misleading translation. ### A clear way to move from diagnosis to delivery #### Understand We review the website, your commercial priorities and the decision you need to make. #### Define You receive a scope with priorities, responsibilities and concrete deliverables. #### Implement I work directly on agreed changes or collaborate with your development and content teams. #### Verify We check the implementation and agree how to follow search and business outcomes. ### Questions worth asking before you choose an SEO partner #### Should all languages share one canonical? Distinct, indexable language versions normally use their own canonical URLs. Hreflang connects equivalent versions; duplicate URLs within one language need a separate decision. #### Does Swedish content need to be a direct translation? No. The service should remain consistent, while vocabulary, examples, buying questions and calls to action reflect the Swedish audience. #### How is Persian handled? Persian copy is written and edited for Persian readers, with a polite conversational tone. RTL layout, mixed Latin terms, punctuation and form behaviour are checked separately. #### What if a translation is not ready? Keep the incomplete page unpublished and out of the language cluster. A language homepage is not the equivalent of a missing service page. #### Can you review an existing multilingual setup? Yes. I can start with a focused review of language URLs and search data, then separate technical corrections from the content work each market needs. ### How to choose a service and plan the work [Choose the work your site actually needs](https://ramfaseo.se/en/services/) ### Sources and language versions - [SV original](https://ramfaseo.se/tjanster/flersprakig-seo/) - [EN original](https://ramfaseo.se/en/services/multilingual-seo/) - [FA original](https://ramfaseo.se/fa/services/multilingual-seo/) --- ## Help shoppers discover the right category, then the right product. > A store can have thousands of products and still make the important ones difficult to find. I connect search demand to category structure, product information and internal links, while controlling the duplicate URLs created by filters and variations. [Original page](https://ramfaseo.se/en/services/ecommerce-seo/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Who this is for For online retailers with weak category visibility, overlapping product pages, faceted-navigation problems or a growing catalogue. My public experience includes work in promotional products, luxury watches and building materials. ### What we work on - Map commercial search intent to categories, subcategories, products and buying guides. - Review filters, sorting, variants, pagination and the URLs that should be discoverable or indexable. - Improve category copy, product detail requirements, breadcrumbs and useful internal links. - Check product availability handling, structured data consistency and performance on store templates. ### What you receive - A category and landing-page plan tied to customer decisions. - Template-level SEO requirements and prioritized technical fixes. - A measurement plan separating search visibility, product discovery and commercial outcomes. ### Planning the scope Stock, pricing, merchandising and checkout decisions remain with your business. Product data must reflect the real offer; markup cannot compensate for missing or inaccurate information. ### Planning this service for your site #### A sensible starting point Choose a category or template with a clear commercial problem first. A shop-wide rewrite is rarely the right starting point when filters or category structure are the underlying issue. #### What to prepare Provide example categories and products, the platform, catalogue structure and how variants, stock changes and discontinued products are handled. Customer or order records are not needed in the first message. #### What changes the scope Catalogue size, filter combinations, product variants and template constraints change the effort. Product data cleaning, photography and checkout development are separate unless agreed. #### How to review the handover Review the agreed category and product templates, internal routes and rules for filters or unavailable products. Confirm product information remains accurate and customer paths still work after changes. ### A clear way to move from diagnosis to delivery #### Understand We review the website, your commercial priorities and the decision you need to make. #### Define You receive a scope with priorities, responsibilities and concrete deliverables. #### Implement I work directly on agreed changes or collaborate with your development and content teams. #### Verify We check the implementation and agree how to follow search and business outcomes. ### Questions worth asking before you choose an SEO partner #### Do you support WooCommerce and Shopify? Yes. The strategy is based on the store's structure and goals, and implementation respects each platform's routing, templates and app limitations. #### Should every filter page be indexed? No. Some filter combinations answer useful search demand; others create near-duplicates. I assess demand, content and crawl behaviour before defining the rules. #### What happens to sold-out products? The right approach depends on whether stock is returning, an equivalent product exists and the page still helps visitors. A consistent policy is more useful than deleting every unavailable product. #### Can you help with category content? Yes. Category pages need to help people choose, understand the range and reach products. Content briefs cover useful comparisons, selection criteria and relevant questions. #### Will you report revenue growth? Revenue is reported when reliable measurement and access exist. I distinguish observed changes from causation and account for stock, pricing, campaigns and seasonal demand. ### How to choose a service and plan the work [Choose the work your site actually needs](https://ramfaseo.se/en/services/) ### Sources and language versions - [SV original](https://ramfaseo.se/tjanster/e-handel-seo/) - [EN original](https://ramfaseo.se/en/services/ecommerce-seo/) - [FA original](https://ramfaseo.se/fa/services/ecommerce-seo/) --- ## Give each page a job in your customer's decision. > More articles are not always the next step. I first examine what your customers need to understand, which pages already answer those questions and where your expertise is missing from the site. The result is a content plan connected to real services. [Original page](https://ramfaseo.se/en/services/content-strategy/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Who this is for For specialist businesses with generic website copy, stores whose categories overlap, or teams publishing regularly without a clear connection to enquiries and sales. ### What we work on - Research customer questions and search intent across discovery, comparison and purchase. - Map topics to existing URLs to identify gaps, overlap and competing pages. - Review titles, headings, introductions, evidence, FAQs and the next action on each priority page. - Connect supporting articles, service pages, authors and examples through useful internal links. ### What you receive - A prioritized content and URL map with a purpose for each page. - Editorial briefs covering audience, structure, supporting evidence and internal links. - Rewritten or optimized priority pages within the agreed scope, with a review process. ### Planning the scope Subject-matter claims need your evidence and review. Writing volume, languages and approval responsibilities are agreed before production; publishing frequency is not a ranking guarantee. ### Planning this service for your site #### A sensible starting point Start with the questions preventing a visitor from choosing: suitability, limitations, process, proof and next steps. If pages cannot be crawled, resolve that obstacle alongside the content plan. #### What to prepare Bring the services you actually deliver, examples of customer questions, existing pages and evidence you are allowed to publish. Identify who can approve factual or specialist claims. #### What changes the scope Research, interviews, original writing, editing, translation and publishing are distinct pieces of work. Agree on which pages and languages need each one. #### How to review the handover Check that each page answers its intended question, distinguishes your offer, supports factual claims and leads to a relevant next step. A word count alone is not a useful acceptance criterion. ### A clear way to move from diagnosis to delivery #### Understand We review the website, your commercial priorities and the decision you need to make. #### Define You receive a scope with priorities, responsibilities and concrete deliverables. #### Implement I work directly on agreed changes or collaborate with your development and content teams. #### Verify We check the implementation and agree how to follow search and business outcomes. ### Questions worth asking before you choose an SEO partner #### Can you improve existing content instead of starting again? Yes. I assess whether a page needs a clearer answer, stronger evidence, a different search intent or consolidation with another page before recommending new content. #### How are topics prioritized? By customer relevance, the business offer, the current site's gaps and the effort required. Search volume alone does not decide what a specialist website should publish. #### Do you write service pages as well as articles? Yes. Service pages, categories, product information, comparison content and guides each play a different role in the customer journey. #### How do you avoid generic AI copy? The brief starts with your actual work, customer questions and evidence. Drafts receive factual and editorial review; unsupported claims and repetitive filler are removed. #### Can you localize content across languages? Yes. The same service can need different examples, terminology and explanations in each language. Language versions are reviewed as complete pages, not sentence-by-sentence substitutions. ### How to choose a service and plan the work [Choose the work your site actually needs](https://ramfaseo.se/en/services/) ### Sources and language versions - [SV original](https://ramfaseo.se/tjanster/innehallsstrategi/) - [EN original](https://ramfaseo.se/en/services/content-strategy/) - [FA original](https://ramfaseo.se/fa/services/content-strategy/) --- ## Make the pages your customers use feel faster. > A slow product page, a jumping headline or a delayed menu can interrupt an otherwise good website. I investigate the pages and interactions that matter, then work on the loading and rendering behaviour behind the problem. [Original page](https://ramfaseo.se/en/services/website-performance/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Who this is for For websites with inconsistent mobile performance, slow templates, intrusive layout shifts or heavy scripts. The review can support a redesign or focus on an existing WordPress, store or JavaScript application. ### What we work on - Compare available field data with repeatable lab tests across important page types. - Investigate LCP resources, image delivery, font loading and render-blocking assets. - Review JavaScript cost, third-party tools, responsiveness and layout stability. - Retest critical interactions, visual appearance and SEO output after changes. ### What you receive - A baseline by template with the main bottlenecks and their likely impact. - Agreed implementation work and budgets for images, fonts and scripts. - Comparable before-and-after tests, with field and laboratory results clearly separated. ### Planning the scope A single Lighthouse score does not describe every visit. Field data needs sufficient real traffic; fixed scores and instant changes to a rolling field dataset are not promised. ### Planning this service for your site #### A sensible starting point Choose the slow page templates and interactions before buying a redesign. Separate a slow server response, a heavy first screen and delayed interaction; they require different fixes. #### What to prepare Send representative URLs, affected devices and the actions that feel slow. Note required scripts, forms, payments and any limits on changing hosting or third-party services. #### What changes the scope Theme code, image delivery, caching and external scripts affect both effort and control. Agree which templates and dependencies can actually be changed. #### How to review the handover Compare equivalent measurements under recorded conditions, then check forms, navigation and visual stability. Field data reflects real visits over time; a single lab score does not establish the whole user experience. ### A clear way to move from diagnosis to delivery #### Understand We review the website, your commercial priorities and the decision you need to make. #### Define You receive a scope with priorities, responsibilities and concrete deliverables. #### Implement I work directly on agreed changes or collaborate with your development and content teams. #### Verify We check the implementation and agree how to follow search and business outcomes. ### Questions worth asking before you choose an SEO partner #### Why can PageSpeed and my own phone feel different? Lab tests use defined devices and network conditions. Real visits vary by connection, device, location and interaction. Both kinds of evidence help diagnose the experience. #### Can the design stay visually distinctive? Yes. Clear typography, useful layout and carefully delivered images can create a strong identity without large animation libraries or unnecessary scripts. #### Do you fix hosting or only front-end code? I examine the full request and rendering path. Hosting, caching, server response and third-party dependencies may be part of the findings; the implementation scope is agreed with the team. #### What are LCP, INP and CLS? They describe loading of the main content, responsiveness to interaction and unexpected layout movement. I connect each metric to the actual page or interaction causing difficulty. #### Will optimization break tracking or forms? Those journeys are part of acceptance testing. Removing a script without understanding its purpose can break useful functionality, so changes are reviewed and tested. ### How to choose a service and plan the work [Choose the work your site actually needs](https://ramfaseo.se/en/services/) ### Sources and language versions - [SV original](https://ramfaseo.se/tjanster/webbprestanda/) - [EN original](https://ramfaseo.se/en/services/website-performance/) - [FA original](https://ramfaseo.se/fa/services/website-performance/) --- ## Make your expertise easier to discover, understand and cite. > People increasingly compare specialists through answers as well as search results. I work on the information those systems can access: what you do, who is responsible, the evidence behind your expertise and the pages that answer a customer's actual question. [Original page](https://ramfaseo.se/en/services/ai-search-visibility/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Who this is for For experts and businesses whose public identity is fragmented, whose service pages are vague or who want a credible way to observe their presence in AI-assisted search. ### What we work on - Review crawl access, rendered page content, canonical URLs and important internal links. - Align person, organization, services and verified external profiles. - Develop answerable pages with specific explanations, sources, authorship and relevant evidence. - Build a fixed observation protocol separating brand mentions, source citations, recommendations and enquiries. ### What you receive - An entity and content gap review connected to your real services. - Prioritized technical and editorial changes for accessible, useful information. - A dated observation log with prompts, surfaces, sources and access limitations. ### Planning the scope No service can guarantee a recommendation by an AI system. Results vary by query, product and context. Missing observations are not treated as zero visibility, and training-bot policy is considered separately from search access. ### Planning this service for your site #### A sensible starting point Start with a specific representation problem: an inaccurate description, an unclear service or missing source information. If the site does not explain the business well, improve those pages first. #### What to prepare Bring the questions that matter to potential customers, the public pages that should support answers and examples with their platform and observation date. Remove personal information from shared examples. #### What changes the scope Entity information, service content, source consistency and observation work are separate tasks. Publishing a special file is not a substitute for a clear, accessible site. #### How to review the handover Check the published facts and supporting pages, then document observations with the question, platform and date. A citation observed once is not a permanent placement, and its absence alone does not identify a technical fault. ### A clear way to move from diagnosis to delivery #### Understand We review the website, your commercial priorities and the decision you need to make. #### Define You receive a scope with priorities, responsibilities and concrete deliverables. #### Implement I work directly on agreed changes or collaborate with your development and content teams. #### Verify We check the implementation and agree how to follow search and business outcomes. ### Questions worth asking before you choose an SEO partner #### Is this a replacement for SEO? No. Accessible pages, useful content and clear identity support both conventional search and AI-assisted discovery. The observation method differs from a conventional ranking report. #### Can you guarantee that ChatGPT will recommend me? No. We can improve information quality and accessibility and test defined queries, but the system controls its answers and sources. #### What counts as a result? A mention, a citation, a recommendation and an enquiry are different events. They are recorded separately with the prompt, date and surface so the report remains interpretable. #### Do I need special AI markup or llms.txt? Not by default. Structured data should match the page. Additional files are considered only when there is a specific consumer and useful maintenance plan. #### How do you handle research limits? Access failures, quotas, personalization and incomplete runs are documented. A short or incomplete panel is not presented as a complete market study. ### How to choose a service and plan the work [Choose the work your site actually needs](https://ramfaseo.se/en/services/) ### Sources and language versions - [SV original](https://ramfaseo.se/tjanster/ai-sokning/) - [EN original](https://ramfaseo.se/en/services/ai-search-visibility/) - [FA original](https://ramfaseo.se/fa/services/ai-search-visibility/) --- ## Know what to work on next, and how you will judge it. > SEO decisions compete with development time, content budgets and daily business needs. I help translate search problems into a workable sequence, with clear responsibilities and measures that make sense for your business. [Original page](https://ramfaseo.se/en/services/seo-consulting/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Who this is for For founders who need a specialist partner, marketing leads coordinating several teams, or businesses that need an independent review of an existing SEO plan. ### What we work on - Clarify commercial priorities, audiences, service lines and the customer journey. - Review Search Console and analytics definitions, including what counts as a real enquiry. - Prioritize technical, content and platform work against available resources. - Agree ownership, review points and how changes will be evaluated. ### What you receive - A practical roadmap with dependencies, priorities and assigned responsibilities. - A measurement specification that separates activity, visibility and qualified outcomes. - Decision support and technical or editorial review through an agreed consulting arrangement. ### Planning the scope The engagement can be a focused consultation, a defined project or continuing support. Frequency, implementation capacity and reporting depth are agreed before work starts. ### Planning this service for your site #### A sensible starting point Choose consulting when priorities, responsibilities or the next investment are unclear. Bring one real business decision; we can use it to make the wider plan more concrete. #### What to prepare Describe your goal, current team, planned releases and constraints. Existing reports help if available, but you do not need to commission another audit before getting in touch. #### What changes the scope A one-off decision session, a written roadmap and recurring team support involve different preparation and follow-up. Agree on the format and implementation role. #### How to review the handover The plan should say what happens first, why, who owns it, what it depends on and how completion will be checked. Make sure the next action is feasible with the people and time available. ### A clear way to move from diagnosis to delivery #### Understand We review the website, your commercial priorities and the decision you need to make. #### Define You receive a scope with priorities, responsibilities and concrete deliverables. #### Implement I work directly on agreed changes or collaborate with your development and content teams. #### Verify We check the implementation and agree how to follow search and business outcomes. ### Questions worth asking before you choose an SEO partner #### Can we start with a single consultation? Yes. Bring the site address, the decision you are trying to make and any relevant search data. We can define a focused review before committing to a larger project. #### Do you work alongside an internal team or agency? Yes. I can help set priorities, review proposals and translate findings into implementation requirements without replacing your existing team. #### What does ongoing support include? An agreed mix of diagnosis, implementation review, content direction and measurement. The exact cadence and available delivery time are part of the scope. #### How is pricing decided? By the website, access, complexity, responsibilities and deliverables. A defined question or project brief makes the estimate more useful than a generic package. #### Which metrics should a service business track? Useful measures can include relevant search landing pages, enquiries and their quality. A form click alone is not a successful lead; the definitions should match the actual business process. ### How to choose a service and plan the work [Choose the work your site actually needs](https://ramfaseo.se/en/services/) ### Sources and language versions - [SV original](https://ramfaseo.se/tjanster/seo-radgivning/) - [EN original](https://ramfaseo.se/en/services/seo-consulting/) - [FA original](https://ramfaseo.se/fa/services/seo-consulting/) --- ## Different businesses. Work shaped around each one. > Explore my work across MTC, Aptiva, Tezkar, legal services, crypto, Shopify, hosting and large product catalogues. Each project has its own priorities, role and evidence. Product work includes Qotuno and the Ramfaseo internal team platform. [Original page](https://ramfaseo.se/en/case-studies/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Different businesses. Work shaped around each one. Explore my work across MTC, Aptiva, Tezkar, legal services, crypto, Shopify, hosting and large product catalogues. Each project has its own priorities, role and evidence. Product work includes Qotuno and the Ramfaseo internal team platform. These accounts are written by Ramin from his direct project work. Client performance data and proprietary strategies remain private. They are not client testimonials or third-party certifications. - [MTC Aptiva: building an HR assessment platform](https://ramfaseo.se/en/case-studies/mtc-aptiva/): From a candidate’s first step to a report the HR team can use. My work on Aptiva connects product design, implementation and the everyday needs of recruitment. - [MTC: connecting SEO with the enquiry journey](https://ramfaseo.se/en/case-studies/mtc/): SEO and digital growth for a corporate-gift business, with attention to what happens after a visitor finds a product. - [Tezkar: making a product catalogue work better on mobile](https://ramfaseo.se/en/case-studies/tezkar/): Technical SEO and digital growth where product discovery, performance and a reliable enquiry journey need to support one another. - [Vedette Legal: local discovery for a legal practice](https://ramfaseo.se/en/case-studies/vedette-legal/): SEO management in a field where finding the right service and trusting the information are closely connected. - [Asacoin: technical SEO in a complex crypto project](https://ramfaseo.se/en/case-studies/asacoin/): An ongoing SEO management engagement connecting server-side issues, technical SEO and on-page work. - [Qotuno: turning a price list into a useful quote page](https://ramfaseo.se/en/case-studies/qotuno/): A product I built for freelancers and service businesses to present their packages, share a quote and give the customer a clear next step. - [Ramfaseo App: a shared workspace for projects and delivery](https://ramfaseo.se/en/case-studies/ramfaseo-app/): An internal team platform I built to connect projects, tasks, collaboration and reporting in one working environment. - [Ramfa SEO: from a language switch to testable language versions](https://ramfaseo.se/en/case-studies/ramfa-seo/): An internal project on ramfaseo.se, supported by HTTP and language checks. The results describe technical behaviour, without claiming traffic growth. - [A reproducible redirect and rollback exercise](https://ramfaseo.se/en/case-studies/redirect-exercise/): Two URL moves, ten HTTP assertions and a controlled rollback. This is a localhost teaching example, not a completed client or WordPress migration. ### More project experience #### Dubai Luxury Watch Shopify SEO My role: SEO Manager for a luxury-watch store on Shopify. This project adds hands-on platform experience to my e-commerce work. It is presented here as a professional engagement, with commercial data and the detailed search strategy kept private. [Dubai Luxury Watch](https://dubailuxurywatch.com/) #### Building Material Dubai SEO for a specialist product catalogue My role: SEO Manager for Building Material Dubai. Its catalogue spans building materials, tools and related products. The project brings a different product-discovery context to my portfolio: buyers need to distinguish practical specifications and find the right product within a broad range. [Building Material Dubai](https://dubaibm.com/) #### Hostnegar SEO in hosting and server services My role: SEO Manager for a hosting and server-services business. This engagement adds a technical-services context to my experience. Visitors need to understand service differences and technical information before choosing a solution; the project-specific plan and internal systems remain confidential. [Hostnegar](https://hostnegar.com/) #### Masterkala SEO at catalogue scale My role: SEO Manager for a large online store. Masterkala adds experience with a substantial catalogue and URL footprint. At this scale, decisions about discoverability have a different operational context from a small service website. Catalogue counts, search data and implementation details are not disclosed. [Masterkala](https://masterkala.com/) ### Sources and language versions - [SV original](https://ramfaseo.se/kundcase/) - [EN original](https://ramfaseo.se/en/case-studies/) - [FA original](https://ramfaseo.se/fa/case-studies/) --- ## MTC Aptiva: building an HR assessment platform > From a candidate’s first step to a report the HR team can use. My work on Aptiva connects product design, implementation and the everyday needs of recruitment. [Original page](https://ramfaseo.se/en/case-studies/mtc-aptiva/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Product development and digital growth #### The business problem An assessment is only useful if candidates can complete it reliably and HR can understand the result. Aptiva needed a connected process, rather than separate forms, answers and files that someone had to assemble afterwards. #### My responsibility As SEO and Digital Growth Manager for MTC and its related projects, I led the work on Aptiva from the platform itself to the HR workflow and reporting. This is a product-development case within that wider role; its outcome is a working recruitment tool. #### What I built and improved The candidate journey covers registration, consent, timed assessments and confirmation. Answers and remaining time survive a page refresh. On the HR side, staff can review candidates, manage assessments and use structured results and PDF reports for each participant. I also worked on mobile readability, loading behaviour and clear recovery when a connection fails. #### The result in use The platform brings participation, review and reporting into one workflow. HR can inspect a participant’s results and prepare a report without rebuilding the information manually. The assessment supports human review; it does not make a hiring decision or provide a medical diagnosis. #### What this demonstrates Digital growth can involve building a useful internal product as well as improving a public website. The public platform and completed implementation support this account. Candidate records, assessment logic and individual reports stay private. These accounts are written by Ramin from his direct project work. Client performance data and proprietary strategies remain private. They are not client testimonials or third-party certifications. [MTC Aptiva](https://mtcaptiva.com/) ### Sources and language versions - [SV original](https://ramfaseo.se/kundcase/mtc-aptiva/) - [EN original](https://ramfaseo.se/en/case-studies/mtc-aptiva/) - [FA original](https://ramfaseo.se/fa/case-studies/mtc-aptiva/) --- ## MTC: connecting SEO with the enquiry journey > SEO and digital growth for a corporate-gift business, with attention to what happens after a visitor finds a product. [Original page](https://ramfaseo.se/en/case-studies/mtc/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### SEO and digital growth #### A different growth problem A corporate-gift catalogue serves people who need to compare options and discuss an order. Search visibility matters, but the route from finding a product to making an enquiry also has to work. #### My role and approach I manage SEO and digital growth for MTC and its related projects. Priorities follow the needs of each site and product, rather than a shared checklist. The work connects technical decisions, catalogue discovery and the actions visitors need to complete. #### One concrete implementation I resolved a post-submission reset in the enquiry flow. Visitors could submit a form and then lose the visible confirmation when the interface reset. The correction keeps the confirmation in place and was checked across the individual and reseller journeys, including validation. #### What the evidence supports Private Search Console records show broader search visibility in the comparable period reviewed. That is a visibility result, not a claim that every traffic or sales measure increased. The enquiry fix has a separate, directly observable outcome: the submission state stays understandable to the visitor. #### The experience behind the work This project combines search responsibilities with practical delivery. The public case describes the business problem and the completed change. Account data, search terms and the detailed growth plan remain confidential. These accounts are written by Ramin from his direct project work. Client performance data and proprietary strategies remain private. They are not client testimonials or third-party certifications. [Magic Trading Company](https://mtc.ae/) ### Sources and language versions - [SV original](https://ramfaseo.se/kundcase/mtc/) - [EN original](https://ramfaseo.se/en/case-studies/mtc/) - [FA original](https://ramfaseo.se/fa/case-studies/mtc/) --- ## Tezkar: making a product catalogue work better on mobile > Technical SEO and digital growth where product discovery, performance and a reliable enquiry journey need to support one another. [Original page](https://ramfaseo.se/en/case-studies/tezkar/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Technical SEO and digital growth #### The practical challenge A product catalogue can be visible in search and still make visitors work too hard. My work on Tezkar connects SEO priorities with the experience of browsing products and reaching the next step. #### My responsibility Tezkar is part of my SEO and Digital Growth Manager remit across MTC-related projects. I worked on technical delivery and the customer journey, with the site's own catalogue and commercial needs guiding the priorities. #### Changes made I reduced unnecessary scripts and styling in the browsing experience, improved the way product imagery and carousels behave on smaller screens, and corrected a responsive issue that could make products disappear when the layout changed. Search, navigation, cart and enquiry paths were checked alongside those changes. #### Observed outcome The delivered changes address concrete loading and usability problems. Private Search Console comparisons also show growth in organic visibility and clicks over comparable periods. Those figures stay private, and the search change is not attributed to a single code fix. #### What carries over to other projects Performance work is useful when the customer can still find, compare and enquire about products. This case shows that connection without exposing the site's keyword plan, internal prioritisation or implementation recipe. These accounts are written by Ramin from his direct project work. Client performance data and proprietary strategies remain private. They are not client testimonials or third-party certifications. [Tezkar](https://tezkar.ae/) ### Sources and language versions - [SV original](https://ramfaseo.se/kundcase/tezkar/) - [EN original](https://ramfaseo.se/en/case-studies/tezkar/) - [FA original](https://ramfaseo.se/fa/case-studies/tezkar/) --- ## Vedette Legal: local discovery for a legal practice > SEO management in a field where finding the right service and trusting the information are closely connected. [Original page](https://ramfaseo.se/en/case-studies/vedette-legal/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Local SEO and legal-service content #### The search problem Someone looking for legal help needs to understand whether a practice handles their situation. Local discovery has to lead to clear service information, rather than a page that simply repeats a search phrase. #### My role I managed SEO for Vedette Legal. My public professional record describes work on technical audits, search-demand research and on-page and off-page optimisation. The engagement ran from April 2024 to October 2025. #### The focus of the work The work connected technical access with the intent behind legal-service searches. Local relevance, service clarity and trust in the information were central to how I approached the project. The detailed search plan and competitive decisions are not part of this public account. #### How I describe the outcome From my direct experience of the project, local visibility and appearances in AI-assisted search are meaningful parts of the outcome. This page is my account of that work, not an independent ranking report. It does not imply a permanent position, a recommendation from every AI service or an endorsement by Google. #### Why this experience matters Legal-service SEO calls for care about what a page promises and who stands behind it. The case demonstrates my experience connecting local discovery, technical SEO and useful service information. Client enquiries and performance reports remain private. These accounts are written by Ramin from his direct project work. Client performance data and proprietary strategies remain private. They are not client testimonials or third-party certifications. [Vedette Legal](https://vedette-legal.com/) ### Sources and language versions - [SV original](https://ramfaseo.se/kundcase/vedette-legal/) - [EN original](https://ramfaseo.se/en/case-studies/vedette-legal/) - [FA original](https://ramfaseo.se/fa/case-studies/vedette-legal/) --- ## Asacoin: technical SEO in a complex crypto project > An ongoing SEO management engagement connecting server-side issues, technical SEO and on-page work. [Original page](https://ramfaseo.se/en/case-studies/asacoin/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Ongoing technical and on-page SEO #### Why the context matters Asacoin is a crypto project. Its SEO work involves both the infrastructure serving the website and the pages people and search engines encounter. A content change alone cannot resolve a problem that starts in the server or delivery layer. #### My role and current scope I manage SEO for the project. The current work includes technical tasks, server-related issues and on-page SEO. These areas are prioritised together according to the site's own needs, rather than treated as interchangeable tasks from a generic plan. #### What I can share This is an ongoing engagement. The public account identifies my responsibility and the technical scope; it does not present pending work as a completed result. Private project records inform the work, while server settings, access details and the executable strategy remain confidential. #### What the experience demonstrates The project adds experience in an environment where technical dependencies and careful content decisions both matter. My role concerns the website and its search performance. This case does not evaluate or recommend financial products. These accounts are written by Ramin from his direct project work. Client performance data and proprietary strategies remain private. They are not client testimonials or third-party certifications. [Asacoin](https://asacoine.com/) ### Sources and language versions - [SV original](https://ramfaseo.se/kundcase/asacoin/) - [EN original](https://ramfaseo.se/en/case-studies/asacoin/) - [FA original](https://ramfaseo.se/fa/case-studies/asacoin/) --- ## Qotuno: turning a price list into a useful quote page > A product I built for freelancers and service businesses to present their packages, share a quote and give the customer a clear next step. [Original page](https://ramfaseo.se/en/case-studies/qotuno/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Product design and development #### The problem behind the product Sending prices as scattered messages makes it harder for a client to compare what is included. Qotuno gives service providers a dedicated page for that conversation, with their packages and contact options together. #### What the product contains The implemented product includes editable packages, branded quote pages, shareable links and a way for a potential client to leave an enquiry. Profession-specific templates provide a starting point, while the export interface produces a PDF or an image for sharing outside the website. #### My contribution This is one of my product-development projects. The work brings together the service offer, the quote-building interface and the page the recipient sees. Mobile presentation matters because a shared quote may be opened straight from a message. #### A concrete output The public Qotuno website explains the product and links to a demo and templates. The case demonstrates a working product concept and implemented interfaces. It does not claim a measured increase in customer sales or disclose user quotes and enquiries. These accounts are written by Ramin from his direct project work. Client performance data and proprietary strategies remain private. They are not client testimonials or third-party certifications. [Qotuno](https://qotuno.com/) ### Sources and language versions - [SV original](https://ramfaseo.se/kundcase/qotuno/) - [EN original](https://ramfaseo.se/en/case-studies/qotuno/) - [FA original](https://ramfaseo.se/fa/case-studies/qotuno/) --- ## Ramfaseo App: a shared workspace for projects and delivery > An internal team platform I built to connect projects, tasks, collaboration and reporting in one working environment. [Original page](https://ramfaseo.se/en/case-studies/ramfaseo-app/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Internal product development #### The operational need A project plan is only useful when people know what they own and what happens next. Ramfaseo App brings project context and day-to-day tasks together instead of leaving progress scattered across separate conversations. #### What is implemented The application contains project and task views, a Kanban workflow, assignments, priorities and deadlines. Team collaboration, task comments, time logs and reporting sit alongside the work. A guided walkthrough helps users understand the workspace, while access to management areas follows the person's role. #### My contribution This is a product I developed around the organisation of delivery. The work connects an overview of ongoing projects with the details a team member needs to act on, rather than presenting a dashboard with no path into the work. #### Public introduction, private workspace The product has its own public entry point; the working areas require sign-in. This case describes capabilities present in the application source. Team records, budgets, conversations and project information are kept out of the public portfolio. These accounts are written by Ramin from his direct project work. Client performance data and proprietary strategies remain private. They are not client testimonials or third-party certifications. [Ramfaseo App](https://ramfaseo.app/) ### Sources and language versions - [SV original](https://ramfaseo.se/kundcase/ramfaseo-app/) - [EN original](https://ramfaseo.se/en/case-studies/ramfaseo-app/) - [FA original](https://ramfaseo.se/fa/case-studies/ramfaseo-app/) --- ## Ramfa SEO: from a language switch to testable language versions > An internal project on ramfaseo.se, supported by HTTP and language checks. The results describe technical behaviour, without claiming traffic growth. [Original page](https://ramfaseo.se/en/case-studies/ramfa-seo/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Own project / technical implementation / 22 October 2026 #### Starting point The earlier website had a limited URL structure and problems with direct access to language versions. The review separated browser observations from findings established by HTTP tests. Existing Insights content stayed on its own addresses. #### Scope and ownership Ramfa SEO owns the project; Ramin Amirhaeri is responsible for its business information. Work covered routing, server-rendered content, language metadata, service pages, contact delivery and publication. This documents our own website and is not a client testimonial. #### Implementation Swedish remained at the root, with English under /en/ and Persian under /fa/. One URL registry drives links, canonicals, hreflang and the sitemap. The contact form distinguishes test mode from delivery. Preview deployments require authentication. #### Verified result The initial release was checked on 22 October 2026: 33 language URLs responded correctly and the independent hreflang checker passed all 33. Unknown addresses were tested for HTTP 404. A labelled email test was accepted by the mail server, and the recipient confirmed arrival in the inbox. #### Evidence and limits Download the dated hreflang result below and rerun the tool with the URL map. An HTML check does not prove Google indexing or Google-selected canonicals. Further pages may be added after this measurement. Traffic, conversions and AI citations require separate time-series measurement. ### Sources and language versions - [SV original](https://ramfaseo.se/kundcase/ramfa-seo/) - [EN original](https://ramfaseo.se/en/case-studies/ramfa-seo/) - [FA original](https://ramfaseo.se/fa/case-studies/ramfa-seo/) --- ## A reproducible redirect and rollback exercise > Two URL moves, ten HTTP assertions and a controlled rollback. This is a localhost teaching example, not a completed client or WordPress migration. [Original page](https://ramfaseo.se/en/case-studies/redirect-exercise/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### Teaching example / controlled HTTP test / 22 October 2026 #### The problem being isolated A URL move can introduce redirect chains, loops or misleading HTTP 200 pages. This exercise focuses on old addresses, relevant destinations and unknown paths before and after rollback. #### The test A temporary local server redirects /old-service/ to /services/technical-seo/ and /old-contact/ to /contact/ with HTTP 308. Both destinations return 200. /unknown/ returns 404. The client does not automatically follow redirects, allowing the first response to be checked independently. #### Rollback The exercise then restores the old route set. The two old addresses return 200, the two new addresses return 404, and the unknown address remains 404. All ten assertions passed in the recorded run. The server shuts down after testing. #### Using the approach in WordPress Replace example paths with a reviewed inventory. Also test posts, media, metadata, database state, plugins, forms and the actual server rules in protected staging. A rollback must cover the systems that changed. This Python exercise does not restore a WordPress database. #### Limits The test establishes HTTP behaviour in a controlled environment. It does not prove preserved rankings after a migration or recoverability of a production system. The template and code below make the exercise reproducible. ### Sources and language versions - [SV original](https://ramfaseo.se/kundcase/omdirigeringstest/) - [EN original](https://ramfaseo.se/en/case-studies/redirect-exercise/) - [FA original](https://ramfaseo.se/fa/case-studies/redirect-exercise/) --- ## Tell me what you want to improve. > Share your website, the problem and your goal. We can then define the next step. Do not send passwords, API keys or sensitive client information. [Original page](https://ramfaseo.se/en/contact/) Language: en. Publisher: Ramfa SEO. Public content reference; navigation and visual presentation are omitted. ### A useful first message - The website or store address - The problem, planned change or business goal - Your platform, team and any relevant deadline ### What happens next I review your message, clarify the scope and discuss whether a focused consultation or a project is the right next step. No passwords are needed in the enquiry. Sending an enquiry does not place an order or start paid work. It gives us a starting point to discuss the scope. [info@ramfaseo.se](mailto:info@ramfaseo.se) ### Sources and language versions - [SV original](https://ramfaseo.se/kontakt/) - [EN original](https://ramfaseo.se/en/contact/) - [FA original](https://ramfaseo.se/fa/contact/)