Frequently asked questions

Inside Web is a Belgian digital agency that develops tailor-made websites (WordPress, Odoo, Next.js, Symfony), iOS and Android mobile applications and artificial intelligence solutions. We also support our clients in SEO and GEO, so that they are visible on Google and in AI assistants.

In Braine-le-Château, in Walloon Brabant. We work with companies in Brussels, Wallonia and across Belgium, meeting on site or remotely, whichever suits you best.

SMEs, sole traders, non-profits, public institutions and established brands. Our work ranges from prestige property and hospitality to e-commerce, the non-profit sector and professional federations.

A first conversation to understand your objectives, a detailed proposal, and then development in stages with regular sign-offs. Once the site is live we look after the technical follow-up and the continued development of your tool, if you would like us to.

Expect a few weeks for a brochure site, and several months for an online shop, an Odoo project or a mobile application. The schedule is set out in the proposal, with clear points of validation.

Because a tool built around your needs is faster, safer and lasts longer than an assembly of themes and plugins. It grows with your business instead of having to be rebuilt every three years.

Yes. The code developed for your project is yours. You are not locked into a proprietary platform.

We offer hosting, maintenance, security and further development through our Care service. You are equally free to take over yourself or to hand the follow-up to another partner: nothing obliges you to stay.

Yes. We start with a technical, SEO and security audit, and then propose either a gradual overhaul or a full rebuild, depending on what best serves your business.

If your company is an SME with an operating base in the Brussels-Capital Region, the digitalisation grant may cover part of the assignment, subject to conditions. The application has to be submitted before the project starts.

Fill in the contact form: three fields is all it takes. A member of the team will get back to you within 24 working hours for a first conversation, with no obligation.

It is a site whose theme is developed specifically for your project, with no purchased theme and no page builder. Inside Web writes every template and keeps plugins to the strict minimum, which makes the site faster, safer and simpler to develop further.

Because these page builders generate heavy code, slow the site down and create a strong dependency on the tool. They suit a quick prototype, not a professional site meant to last several years.

Yes. The admin area is designed around your content: text, images, pages, news and products. You manage the content independently, while the structure and the design stay protected.

As few as possible, usually a handful of proven plugins for custom fields, multilingual content or e-commerce. Everything else is developed inside the theme, which cuts down the risk of security issues and conflicts.

Far longer than an assembled one. With no dependency on a theme or a page builder, it develops through successive releases and stays fast for five years and more, where assembled sites are often rebuilt after two or three.

In most cases the slowness comes from an overweight theme, a page builder or too many plugins, and sometimes from the hosting. An audit identifies the cause; the answer ranges from targeted optimisation to rebuilding the theme.

Yes. We audit the code, the plugins, the security and the SEO, and then propose either a gradual clean-up or a bespoke rebuild. Existing content is kept and migrated.

Not if it is properly prepared. We map the existing URLs, put 301 redirects in place, keep the content that performs and check indexing once the site is live.

Yes. We build bespoke WooCommerce shops with online payments, stock management and an optional connection to Odoo, so orders, customers and invoicing sit in one place.

The WordPress core is solid and regularly updated. Most vulnerabilities come from third-party plugins. By keeping those to a minimum, maintaining the site and hardening the server, a high level of security is entirely achievable.

If you would like it to be, yes. We regularly build sites in French, Dutch and English, with clear translation management and proper search visibility for each language.

No, and we say so. WordPress is excellent for an editorial site or an online shop run by your own team. For a business platform, a SaaS product or a site with no editorial administration, we recommend bespoke development in Next.js or Symfony.

Odoo is a modular business management system that brings together a website, e-commerce, CRM, sales, stock, accounting, invoicing and many other functions in one place. You switch on the modules you need and add the others as you grow.

Yes. Its modular design lets you start with a few applications, invoicing and CRM for instance, and extend from there. It is often the first genuine ERP that fits a Belgian SME.

Community is the open source edition, with a narrower functional scope. Enterprise adds more modules, the mobile application, support and upgrades. The right choice depends on what you actually need.

Odoo Online is the simplest SaaS option but does not accept custom-developed modules. Odoo.sh and hosting on a dedicated server both allow bespoke development. We guide you according to how much customisation you need.

If the complexity of your business sits in the management side (stock, B2B, production), Odoo. If it sits in the brand experience and the content, WooCommerce. If it sits in both, Inside Web connects WooCommerce to Odoo.

Yes. We synchronise products, prices, stock, customers and orders between WooCommerce and Odoo. The site stays fast and editorially free, while management is centralised in Odoo.

Yes. Odoo supports sending and receiving invoices over the Peppol network, which has been mandatory for B2B exchanges in Belgium since 1 January 2026. We configure and test that flow with you.

An analysis of your processes, a choice of modules, configuration, data migration, bespoke development where needed, training for your team, and then go-live. We work in phases so the tool is put to use quickly.

From a few weeks for a standard scope to several months for a roll-out across departments. We proceed in phases rather than switching everything over at once.

Yes. Customers, products, sales history and invoices can be imported into Odoo once cleaned up. Data migration is part of the scoping work.

Odoo publishes a major version every year. Custom modules have to be adapted when migrating. We develop in a way that keeps those adaptations light, and we plan version upgrades with you.

Yes. We connect Odoo to AI models to classify incoming enquiries, prepare quotations, enrich product records or produce summaries, working directly from your own data.

By taking on the repetitive work: answering frequent questions, sorting emails, drafting quotations, summarising documents, enriching product records. The point is to free up time for the work that adds value.

It is an assistant that answers from your own documents (catalogue, procedures, knowledge base) rather than from general knowledge. The technique used, known as RAG, allows it to cite its sources and sharply limits invented answers.

A chatbot answers questions. An AI agent acts: it checks stock, creates a task, prepares a quotation or updates a customer record in your tools, following rules and permissions you define.

Yes, provided the architecture is right. We favour providers that do not use data sent through their API to train their models, options for European hosting, and self-hosted open source models where confidentiality demands it.

It can be. That means keeping the personal data sent to a minimum, documenting the processing, informing users and choosing compliant processors. We build these points in from the scoping stage.

For most SME uses, the obligations are mainly about transparency: making clear that someone is interacting with an AI or that a piece of content was generated. Uses classified as high risk face heavier requirements. We assess your situation during scoping.

Yes. That is why we limit the assistant to verified sources, show those sources, define what it must not do, and require human validation for sensitive decisions.

With a scoping workshop: we list the tasks that eat time, pick the use case with the best effort-to-impact ratio, and define what success looks like. The prototype follows immediately.

A working prototype on a well-defined use case usually takes a few weeks. Moving to production then depends on the integrations needed and on how heavily it will be used.

We choose the model to suit the need: models from OpenAI, Anthropic, Google, or open source models. No model is best at everything; we weigh quality, speed and confidentiality for your particular case.

No. It removes repetitive tasks and speeds up production, but supervision, client relationships and decisions stay human. The companies that benefit most are the ones that train their people to use it.

Yes. We integrate AI into websites, online shops, mobile applications and Odoo, so that it works where your data and your people already are.

An MVP usually takes a few months. A richer application, with a back office and integrations, takes longer. The schedule is broken into sprints with regular testable releases.

Cross-platform (React Native) means a single codebase for iOS and Android, which speeds up development and simplifies maintenance. Native is justified for very specific needs in graphics performance or advanced hardware access.

An MVP (minimum viable product) is a first version of the application limited to the essential features. It lets you test the idea with real users before building a full version.

Scoping the features, designing the screens, development in sprints with test builds on your own phones, publication on the stores, and then follow-up. You watch the application take shape week by week.

Yes. We prepare the listings, the screenshots and the privacy information, and manage the submission. The application is published under your own developer account, so that it stays yours.

Yes, for the features that allow it. Data is stored locally and synchronised once the connection returns, which is essential for applications used in the field.

Yes. Notifications can be triggered manually from the back office or automatically by events: a new order, a reminder, an alert.

Yes. Your site, your shop or your Odoo can serve as the source of data through an API: products, orders, customer accounts and content stay in step between web and mobile.

We offer a follow-up service covering compatibility with new versions of iOS and Android, fixes and further development. An application left unmaintained eventually misbehaves or is removed from the stores.

Yes: a conversational assistant, intelligent search, image recognition, personalised recommendations. AI is integrated through an API and stays controllable from the back office.

Sometimes, yes. A PWA installs from the browser without going through the stores, but what it can do remains more limited, particularly on iOS. We recommend whichever suits the way your app will be used.

The first effects usually appear after three to six months, depending on the competition, the site's history and the scale of the corrections. Technical gains can come faster; authority is built over time.

A serious audit covers indexing, speed, URL structure, internal linking, structured data, content quality, keywords, inbound links and the competition. It ends in a prioritised action plan, not a list of 200 warnings.

Google Ads brings traffic immediately, for as long as the campaign runs. SEO builds lasting visibility. The two complement each other: advertising tests the keywords, SEO establishes presence over time.

The most common causes are a page that is not indexed, a technical block, content that is too thin, stronger competition or a lack of inbound links. An audit identifies the real cause within days.

It covers everything that lets search engines crawl, understand and index a site: speed, rendering, structure, markup, sitemap, redirects and structured data. It is the foundation without which content does not perform.

By optimising your Google Business Profile, gathering customer reviews regularly, keeping your contact details consistent across the web, and creating local pages that are genuinely useful rather than copies with the town name swapped.

Only if it is badly prepared. With a URL map, 301 redirects, the content that performs kept in place and proper monitoring after launch, a rebuild generally improves search visibility.

Google does not penalise content because AI helped produce it, but because it is useless, generic or mass-produced to game the rankings. Content that is reviewed, enriched by real expertise and genuinely useful continues to perform.

Yes. Generative engines lean heavily on pages that are well ranked and well structured. Good SEO is the foundation of GEO; the two are worked on together.

Through positions on the target queries, organic traffic, the conversions that traffic produces, and visibility in generated answers. We report on business indicators, not only on ranking charts.

Yes, through our Visibility service, which combines SEO and GEO: technical monitoring, content production, continuous optimisation and regular reporting.

GEO, or Generative Engine Optimisation, covers the practices that increase the likelihood of a company being mentioned and cited in the answers of generative AI such as ChatGPT, Gemini, Perplexity and Google's AI Overviews.

No, it extends it. Generative engines rely largely on content that is well indexed and well structured. Without solid SEO, GEO has little to work with; without GEO, SEO loses part of the visibility that is moving towards generated answers.

By publishing clear content that answers your customers' questions directly, keeping the information about your company consistent everywhere on the web, earning mentions on reliable third-party sources, and making your site technically accessible to the crawlers.

No, not in the organic answers. Citation depends on the quality, the clarity and the reputation of the sources. That is precisely what GEO works on.

Chiefly ChatGPT, Google Gemini and the AI Overviews, Perplexity, Microsoft Copilot and Claude. Their sources and their behaviour differ: a GEO strategy covers them together rather than one alone.

We define a set of real questions your customers ask, test them regularly against the main assistants, and track the citation rate of your company and your competitors over time.

Technical and content corrections can take effect within weeks on engines that consult the web in real time. Presence in a model's general knowledge builds more slowly, at the pace of its updates.

A picture of what AI currently says about your company, a comparison with your competitors, an analysis of your content, your structured data, the consistency of your entity and your site's accessibility to crawlers, together with a prioritised action plan.

It is not essential: no major engine has committed to using it and Google has said it does not consult it. Putting one in place costs almost nothing, however, so we add it as a complement without treating it as a main lever.

If you want to be cited, yes, at least those belonging to engines that display sources. We check that your robots.txt and your firewall are not blocking those crawlers by accident.

Yes. It describes your company, your services, your addresses and your answers to frequent questions explicitly, which reduces ambiguity and makes your content easier for engines to interpret correctly.

Yes. Users increasingly ask an assistant to recommend a provider near them. A well-kept Google Business Profile, regular reviews and consistent information weigh directly on those recommendations.

When the heart of the project is business logic (workflows, user roles, a configurator, registrations, subscriptions) rather than publishing content, or when the site needs no editorial administration at all. Forcing that kind of project into a CMS makes it heavier and more fragile.

Next.js for responsive web applications, SaaS products and exceptionally fast sites, and Symfony for robust business platforms, with PostgreSQL, Docker and APIs tying everything together. The choice follows the project and its long-term maintainability.

Yes: user accounts, subscriptions and payments, dashboards, transactional email, APIs and a companion mobile application. We prefer to start with an MVP to validate the market before broadening the scope.

Yes. Content is version-controlled alongside the code and deployed automatically. That works beautifully when a technical team runs the site; if your own people need to publish, we add an administration interface to suit.

No, provided it is built on a recognised framework, documented and tested. Next.js and Symfony have large communities, which guarantees longevity and the ability to find other developers.

Yes. The code developed for your platform is yours and can be picked up by another team if need be.

Yes. We integrate ERP systems such as Odoo, payment providers, CRM, email marketing tools and third-party APIs so that the platform fits into the way you already work.

Hosting on managed servers, updates, monitoring, automatic backups, security hardening, and the work needed for fixes and small improvements.

On servers managed and monitored by our own team, in Europe. Each server is configured and hardened for the technologies it runs.

Daily, kept for several days and stored separately from the main server. A restore can be carried out quickly if something goes wrong.

We isolate the site, establish how the intrusion happened, clean up or restore a healthy version, close the weakness and strengthen the protection so it does not happen again.

Because software, server languages and threats keep moving. An unmaintained site gradually becomes slower, more vulnerable and incompatible with recent browsers and services.

Yes, following a technical audit. If the site carries significant risks we tell you, and propose the corrections needed before migrating.

Performance, SEO fundamentals, basic security, accessibility and several signals that matter to generative engines. It gives you an immediate view of what needs fixing first.

No. Enter your site's address and the diagnosis starts straight away.

The in-depth audit examines the code, the architecture, the content, the competition and your visibility in AI assistants, and then turns all of it into actions ranked by impact.

Usually a few working days, depending on the size of the site. The findings are talked through in a meeting so your questions get answered on the spot.

No. The report is precise enough for your own team or another provider to work from.

It is a form of support from the Brussels-Capital Region, managed by Brussels Economy and Employment, covering part of the cost of an external digitalisation consultancy assignment: website, internal processes or IT security. It replaced the former web grant.

SMEs with at least one operating base in the Brussels-Capital Region and active in an eligible sector according to their NACE-BEL code. Among other conditions, the company must have an economic purpose and be up to date with the filing of its annual accounts.

The basic rate is 25 % of eligible expenditure. Increases apply for start-ups and for companies recognised as exemplary on environmental or social grounds, up to a maximum of 70 %, within the annual ceiling set by the Region.

At the latest the day before the assignment begins, through the MonBEE online platform. An assignment started before the application is submitted is not eligible: that is the most common mistake.

Among others, the provider's proposal valid at the time of the application, their curriculum vitae, a bank statement, an extract from the commercial register and, where applicable, proof of social or environmental exemplarity. Inside Web supplies the documents that concern us.

The assignment must run for six months at most and address a one-off problem for which the company does not have the skills in house. Permanent subcontracting is not eligible.

Brussels Economy and Employment notifies its decision within a maximum of four months of receiving a complete file. The assignment may nevertheless start the day after the application is submitted.

After the assignment. You have twelve months from the decision to grant it to send in the supporting documents; the grant is then paid in a single instalment.

Yes. It forms part of the company's taxable income and must appear in its tax return.

Yes. The conditions concern the provider's profile (specialisation, experience, independence) and the location of the beneficiary company, which must be in Brussels.

No, the digitalisation grant is reserved for companies with an operating base in the Brussels-Capital Region. Walloon companies fall under other regional schemes.

WooCommerce is WordPress's open source e-commerce plugin. It lets you manage a catalogue, stock, orders, customers and online payments straight from the WordPress admin area, with no commission paid to a platform.

Yes, provided it is properly built. A shop with a few dozen products and a catalogue of several thousand references both work very well with a light theme, suitable hosting and an optimised database.

Bancontact, Visa and Mastercard, Apple Pay, Google Pay and bank transfer, through providers such as Stripe or Mollie. Inside Web sets up the methods your customers actually use, in Belgium and abroad.

Yes. WooCommerce handles VAT rates by country and can be configured for the OSS one-stop shop, which simplifies VAT reporting for distance selling to consumers within the European Union.

Yes. Inside Web synchronises products, prices, stock, customers and orders between WooCommerce and Odoo. The shop stays fast and editorially free, while management and invoicing are centralised in Odoo.

Because it loads code written for every conceivable use, which slows the shop down and complicates every change. A bespoke theme is faster, safer and matches your catalogue and your brand exactly.

As few as possible: WooCommerce, the payment provider's module and a handful of proven plugins where they add real value. Filters, blocks, delivery rules and exports are developed to measure.

Yes. Products, stock, orders, promotions and content are all managed from the WordPress admin area, with an interface designed around your team. We train the people who run the shop day to day.

Yes. We audit the shop, identify the superfluous plugins and the causes of slowness, and then propose either a gradual clean-up or a rebuild. Products, customers, orders and search rankings are preserved.

It starts on solid ground: fast pages, structured product pages, Product data for Google, categories designed around search and clean URLs. Search visibility is then built over time with content and monitoring.

Yes. Card details do not pass through your shop: they are handled by the certified payment provider. The shop's security then rests on code you control, regular updates and hardened hosting.

Shopify lets you start quickly on a simple catalogue, within the framework of a proprietary platform. A bespoke WooCommerce shop suits brands that want to control their shop, their data and their content, with no ceiling on customisation.

Yes. Inside Web develops connectors that automatically synchronise products, prices, stock, customers, orders and invoices between a WooCommerce shop and Odoo, with a log of the exchanges and recovery in the event of an error.

Products and their variants, prices and price lists, stock by warehouse, customers and addresses, orders, delivery statuses, invoices and payments. The scope is defined together according to what you need.

Important events, such as a new order, are passed across almost instantly. Large updates, such as a complete catalogue, are scheduled at regular intervals so the shop is not slowed down.

Generally Odoo is authoritative for products, prices, stock and invoicing, and WooCommerce for editorial content and the buying experience. That split is adapted to your organisation during scoping.

The connector talks to Odoo through its external API. Depending on the Odoo plan you hold, that access may require a particular subscription. We check this point with you before starting, along with the Odoo.sh and dedicated hosting options.

No. Exchanges with Odoo are handled in the background, outside the buying journey. Visitors experience no additional waiting while browsing or paying.

The shop keeps selling. Orders are queued and passed across automatically as soon as the connection returns. Every failure is logged and flagged.

Yes. Variants, attributes, per-customer or per-group pricing, payment terms and multiple warehouses are taken into account from the design stage, where generic modules often reach their limits.

Yes. Invoices are created in Odoo, which handles delivery over the Peppol network, mandatory for B2B exchanges in Belgium since 1 January 2026. Consumer customers receive a conventional invoice.

Yes. We audit the shop and the existing data, clean up the references where needed, and then put the synchronisation in place without interrupting sales.

It depends on the scope and on the quality of the existing data. A connector limited to orders and stock is set up far more quickly than a full synchronisation with B2B and multiple warehouses. The schedule is set after scoping.

The connector is tested before every significant version upgrade. Because it is developed and maintained by the same team, the adaptations are under control rather than dependent on a third-party publisher.

Not if it is properly prepared. Inside Web inventories every existing URL, keeps the content that performs, puts a 301 redirect in place for each old address and monitors indexing in Google Search Console after go-live.

Yes. Text, images and page structures are extracted from the builder's format, cleaned up and reintegrated into a bespoke theme. You keep your content without keeping the weight or the dependency.

Pages built with the builder lose their layout, and often display technical codes in place of the content, particularly with Divi and WPBakery. That is why moving off a builder is prepared with a genuine content migration.

If the site rests on a healthy foundation and the design suits you, a clean-up may be enough: clearing out plugins, optimisation and hardening. If the site depends on a page builder or a purchased theme that is hard to develop, a rebuild is generally the better investment over the medium term.

Yes. The new site is built on a separate test environment. The old site stays online until the switch-over, which takes a few minutes at a moment you choose.

It depends on the volume of content, the number of templates and the features involved. A brochure site is rebuilt in a few weeks; a content-rich site or a shop takes longer. The schedule is set after the audit.

Yes. Wix offers no complete export of a site: the content and images are recovered and then rebuilt in a bespoke WordPress theme. You become the owner of your site and free to choose your hosting.

We keep them where they are good. Where a clearer structure is called for, each old URL is 301-redirected to its new address, which passes on its search history.

As far as possible. Articles, pages, products and media are migrated by script and then checked. Content trapped in a page builder needs extra cleaning to end up with a clean structure.

The most common causes are a page builder, an overweight multipurpose theme, a large number of plugins, unoptimised images and unsuitable hosting. The audit establishes how much each contributes before any decision is taken.

Yes. If WordPress suits your business, the rebuild keeps WordPress and replaces only the theme, the superfluous plugins and the content structure. Your team keeps an admin area they know, in a simpler form.

It is the best moment. Page structure, markup, speed, structured data and content are all rethought at the same time, which often means starting again with a site that ranks better than the old one.

It is an assistant that answers from your company's content, such as your catalogue, your documentation or your procedures, rather than from general knowledge. Inside Web uses the RAG technique for this, which finds the relevant passages before writing the answer.

RAG, for Retrieval-Augmented Generation, combines a search through your documents with writing by an AI model. The assistant first finds the relevant information in your sources, then frames its answer from that, which sharply limits invention.

In the vast majority of cases, no. With RAG the model is not modified: your content is indexed and consulted at the moment of each question. An update to your documents is therefore taken into account without any retraining.

The risk exists with any AI, but it is greatly reduced when the assistant is limited to your sources, cites the passages it used and is configured to recognise when information is missing. Testing against real questions comes before any launch.

The pages of your site, your product catalogue, documents in PDF, Word or spreadsheet form, a knowledge base, and depending on the project data from Odoo, from your online shop or from other tools through an API.

On your website or shop, in a mobile application, in an internal tool for your team, or in other conversation channels depending on the project. The same knowledge base can serve several channels.

Yes, if the architecture is right. We favour providers that do not use data sent through their API to train their models, options for European hosting and, where confidentiality demands it, self-hosted open source models.

It can be. That means telling users clearly they are talking to an AI, limiting the personal data processed, documenting the processing and choosing compliant processors. These points are built in from the scoping stage.

Yes. Today's models understand and write in many languages, including English, French and Dutch. The assistant answers in the language of the question, even where your sources are written in another.

It says so clearly and offers an alternative: contacting your team, leaving their details or visiting a specific page. Those unanswered questions are then reviewed so the sources can be enriched.

A first working assistant on a well-defined scope usually takes a few weeks to build. The timing depends above all on the quantity and quality of the content to be gathered, and on the integrations required.

Yes. The number of conversations, the most frequent questions, the share of questions answered, hand-overs to a person and the enquiries generated all let you follow its real value and improve it continuously.

An AI agent is a program that understands a situation, decides the steps to follow and acts in your tools: creating a task, preparing a quotation, updating a customer record. Unlike a simple assistant, it does not merely answer, it carries out the work.

Classic automation chains fixed actions according to rules set out in advance. An AI agent can handle variable situations: an email written freely, an attachment, an incomplete enquiry. The two approaches often sit side by side in one process.

Sorting incoming enquiries, preparing quotations, chasing quotations or invoices, enriching product records, extracting information from documents and writing regular reports are among the most rewarding cases.

Yes. Inside Web connects agents to Odoo to read and create quotations, contacts, tasks or invoices, with rights limited to what the agent has to do. Sensitive actions go through approval.

Yes, like any person or any piece of software. That is why we set human approval points for important actions, limit permissions and record every action. A pilot phase on real cases comes before any wider roll-out.

Yes. You decide what it does alone, what it prepares for approval and what it passes to a person. A detailed log lets you review every decision and every action at any time.

The agent reaches only the data its task requires, through dedicated access. We favour model providers that do not use data sent through their API for training, options for European hosting and, where necessary, self-hosted models.

No. Agents connect to the tools you already have, such as Odoo, your mailbox, your CRM or your online shop, as long as they offer a way to exchange data such as an API. The agent adapts to your organisation, not the other way round.

With a process that is frequent, time-consuming and well defined, and whose current cost in time can be measured. A first agent on that ground proves its value quickly before you automate anything else.

A pilot agent on one well-defined task usually takes a few weeks. The timing depends above all on how many tools have to be connected and on how clear the starting process is.

They replace tasks, not people. The time freed from re-keying, sorting and chasing goes back into client relationships, advice and decisions, where people make the difference.

By comparing the time spent on the task before and after, along with the volume handled, the response time and the error rate. Those indicators are set at the outset so you can decide objectively whether to extend the automation.

Three conditions have to be met: a site accessible to OpenAI's crawlers, in particular OAI-SearchBot, content that clearly answers your customers' questions, and a company described consistently on your site and on reliable third-party sources. Inside Web works on all three levers and measures the citations obtained.

No, not in the organic answers. Citations depend on the relevance, the clarity and the reputation of the sources. That is precisely what GEO improves.

GPTBot collects content that may be used to train OpenAI's models. OAI-SearchBot indexes sites for ChatGPT's search answers. They are configured separately: you can allow OAI-SearchBot in order to be cited while blocking GPTBot for training.

No. Blocking GPTBot concerns model training. Presence in ChatGPT's search answers depends on OAI-SearchBot. Blocking OAI-SearchBot, on the other hand, does stop your pages being cited there.

The most common cause is a firewall or an anti-bot service blocking unrecognised visitors. Other frequent causes are content rendered only in JavaScript, pages that lack clarity, or a company too rarely mentioned elsewhere on the web.

ChatGPT has its own indexing crawler, OAI-SearchBot, and also relies on search partners. Good indexing in Bing remains an advantage. Ranking well on Google helps above all for the AI Overviews and for Gemini.

Engines that consult the web in real time can take an improved page into account within days or weeks. Being mentioned spontaneously in a model's general knowledge takes longer, at the pace of its updates.

Its effect is unproven: no major engine has committed to using it and Google has said it does not consult it. We put one in place because it costs almost nothing, but the decisive levers remain crawler access, content quality and the company's reputation.

Yes. It describes your organisation, your services, your address and your answers to frequent questions explicitly. It reduces ambiguity and makes it easier for answer engines to interpret your pages correctly.

By putting to it, and to the other answer engines, the questions your customers would genuinely ask, and noting the citations, the sources used and the accuracy of the information. Inside Web carries out that monitoring each month on a question set defined with you.

Correct the source. Errors often come from outdated or contradictory information on the web. Updating your site, your Google Business Profile and directory entries, and then publishing clear, dated information, gradually restores an accurate description.

Yes. Users increasingly ask assistants to recommend a provider near them. A complete Google Business Profile, regular reviews and consistent local information weigh directly on those recommendations.

An MVP, or minimum viable product, is the first version of an application limited to the essential features. It is dependable enough to be used by real people, so that the idea can be validated and the rest of the development guided by real data.

Because you can never tell in advance which features users will genuinely use. An MVP lets you check the market's interest quickly, limit the initial investment and build what follows on what works.

A well-scoped MVP usually takes a few months, from scoping to publication. The timing depends on the number of screens, the features chosen and the integrations required. The schedule is set after the scoping workshop.

No. An MVP has fewer features, not less quality. The interface has to be polished and the application dependable, otherwise user feedback will be about the flaws rather than about the idea.

Yes. Inside Web develops cross-platform with React Native and Expo: one codebase produces an application for iOS and one for Android, published on the App Store and Google Play.

Yes, that is the point. The architecture is designed to grow from the start: the MVP becomes version 1, and new features are added without starting over.

Through TestFlight for iPhone and Google Play's testing tracks for Android. A group of testers installs the application, uses it in real conditions and reports problems before the official release.

Yes. The application is published under your own developer account, so that it remains yours. For Google Play an organisation account is advisable: some recent personal accounts have to run a closed test before they are allowed to publish.

You do. The source code, the store accounts and the data are yours. You remain free to develop the application further with Inside Web or with another team.

By setting measurable indicators at the outset: active users, retention after a few weeks, completion of the main action, and qualitative feedback. That data decides what comes next.

Sometimes, yes. A PWA lets you test a use case without going through the stores. But if the experience relies on notifications, offline use, the camera or a presence in the stores, a native cross-platform application gives more representative results.

It has to be from the very first version. Consent, data minimisation, a privacy policy and the declarations required by the App Store and Google Play are part of the development, not added afterwards.

Local SEO covers the work that puts a company in Google Maps and in the local results block when a customer looks for a product or service in a particular area. It rests on the Google Business Profile, reviews, consistent information and the local content of the site.

You need a verified, complete and accurate Google Business Profile: the right categories, services, opening hours, area served, photos and regular reviews. A site consistent with the profile and identical information on other platforms then strengthen the ranking.

Google states that it relies mainly on three criteria: the relevance of the business to the search, the distance from the person searching, and the prominence of the company, which takes reviews and mentions online into account.

Yes. The number, the regularity and the quality of reviews, together with the replies given, contribute to a business's prominence and reassure customers. Google does, however, forbid buying reviews or rewarding customers in exchange for one.

Yes, always, calmly and professionally. A factual reply offering a solution shows future customers that the company listens. A negative review handled well often inspires more confidence than a perfect score with no replies.

A service business can define an area served in its Google Business Profile and create genuinely useful pages on its site for the areas it covers. Creating false addresses is forbidden and risks having the profile suspended.

NAP stands for Name, Address, Phone. That information has to be strictly identical on your site, your Google profile, Bing Places, Apple Business Connect and directories, so that search engines can identify one and the same business beyond doubt.

It is strongly advisable if part of your customer base is French or Dutch speaking. Searches in those languages use different words and sometimes different municipality names. A version written for that audience, with correct hreflang tags, lets you appear on those searches.

Corrections to the profile and to your information can take effect within weeks. Prominence, built through reviews and mentions, grows over several months. Results also depend on the competition in your sector and your area.

Recognised and specialist directories remain useful, above all for consistent information and for prominence. What counts is quality and accuracy, not mass listings in low-value directories.

Yes. When somebody asks an AI assistant for a provider nearby, it draws on local information available online: business profiles, reviews, websites and directories. Complete and consistent information improves your chances of being mentioned.

Yes, and it is even desirable for posts and replies to reviews. Inside Web sets up an optimised profile, defines a simple process and trains your team, then handles the follow-up if you would like.

Yes. Odoo offers an e-commerce application built into the same system as stock, sales, invoicing and CRM. Inside Web builds bespoke Odoo shops, matched to your brand guidelines and to your management rules.

Everything sits in one system: the stock displayed is the actual stock, orders arrive straight into the management system, invoices are generated automatically and customers find their documents in a portal. There is no connector to maintain between the shop and the ERP.

Yes, it is one of its strengths. Price lists by customer or by group, prices excluding VAT, payment terms, a customer portal with order and invoice history, and quick reordering are all available as standard.

If management sits at the heart of your business, as in B2B, distribution or with several warehouses, Odoo is often the better choice. If brand experience and content take priority, a bespoke WooCommerce shop connected to Odoo offers more freedom.

Odoo integrates several payment providers, including Stripe and Mollie, which support Bancontact, bank cards and mobile wallets among others. The choice depends on your customers and on your business.

Yes. Odoo manages delivery methods, calculates costs and offers connectors to several carriers for generating labels and tracking shipments. We configure the options that suit your shipping.

Odoo provides the fundamentals, such as meta tags, a sitemap and clean URLs. Inside Web strengthens those foundations with a structure designed around search, product structured data and performance optimisation.

Yes. Beyond the standard templates, we adapt the theme to your brand guidelines and develop bespoke blocks and templates. The freedom nevertheless remains more constrained than with a fully bespoke site.

Yes. Odoo's e-commerce and point of sale share the same stock and the same customers. A sale in store updates online availability, and the other way round.

Yes, for business customers. Odoo supports sending invoices over the Peppol network, mandatory for B2B exchanges in Belgium since 1 January 2026. Consumer customers receive a conventional invoice.

Yes. Products, customers and order history can be carried across into Odoo once the data is cleaned up. We also prepare redirects from the old URLs so search visibility is preserved.

Yes. Odoo runs several websites from one database and several languages per site, which suits the Belgian market in French, Dutch and English well.

It is an extension of Odoo developed specifically for your company, in Python, to add business rules, screens, documents or integrations the standard features do not cover. The module is added to Odoo without modifying its original code.

When standard configuration, Odoo Studio or a dependable existing module cannot reproduce your process without a workaround. Inside Web always checks those options before proposing development, to keep bespoke code to a minimum.

No. The Odoo Online SaaS edition does not allow modules developed in Python to be installed. Custom modules require Odoo.sh or hosting on a dedicated server. We point you towards the right option before starting.

Odoo Studio lets you add fields, modify views and create simple automations without coding. A custom module allows advanced business logic, complex calculations, integrations and automated processing that Studio handles poorly or not at all.

It requires adapting at each major version. By developing only what is necessary, through inheritance and following Odoo's conventions, that adaptation stays manageable. We plan and carry out those migrations with you.

You do. The code developed for your company is yours, version-controlled and documented, and can be picked up by another competent team if need be.

Yes, following a code audit. We check its quality, its compatibility with your version of Odoo and any risks involved, and then propose correcting it, developing it further or rewriting it as appropriate.

Many are, particularly those maintained by active communities such as the OCA. Others are barely looked after. We assess every module before installing it: code quality, compatibility and maintenance activity.

Yes, provided that system offers a way to exchange data such as an API, import files or an accessible database. An integration module then keeps the useful data in step between the two systems, with error tracking.

It depends on the complexity of the rules and on the number of integrations. A targeted adjustment can be delivered quickly; a module that reshapes an entire process takes several iterations. The schedule is set after the specification.

Always. It is developed and tested on a copy of your database, validated by your users during acceptance, and then deployed at a planned moment so your work is not disrupted.

Yes. A module can call an AI model to classify enquiries, extract information from documents, write descriptions or prepare quotations, working directly on your Odoo data and with limited rights.

The most common causes are a page builder or an overweight multipurpose theme, a large number of plugins, unoptimised images, no server-side caching and unsuitable hosting. An audit measures how much each contributes before anything is done.

They are three indicators through which Google measures the real experience of visitors: LCP for how quickly the main content appears, INP for responsiveness to interactions, and CLS for visual stability. They count for search visibility and for the conversion rate.

It can improve matters, but it does not address the causes: a heavy theme, too many plugins or badly optimised images stay slow even when cached. Inside Web favours caching configured at server level and a reduction in the code being loaded.

The WordPress core is solid and actively maintained. The great majority of vulnerabilities come from third-party plugins and themes, often left un-updated. A site with few plugins, properly maintained and hosted on a hardened server, reaches a good level of security.

Not necessarily. Many protections work better at server level: firewall, blocking unused entry points, limiting logins, security headers. We add a plugin only where it provides protection the server does not cover.

Change the admin and hosting passwords immediately, then have the site analysed to find the way in. The site has to be cleaned or restored from a healthy backup, the weakness closed and the site monitored, otherwise the intrusion happens again.

Common signs are redirects to other sites, unknown pages or links, a warning from Google or the browser, administrator accounts you did not create, or a sudden slowdown. An analysis of the files and the database confirms the infection.

Security updates should be applied promptly, ideally within days of release. Major updates are tested first on a test environment to avoid taking the live site down.

Not always. You have to check their frequency, how long they are kept, whether they are stored away from the server and, above all, whether a restore genuinely works. We set up off-site backups and test the restore.

It can if the optimisation is done blind, for instance by combining or deferring scripts without checking. We work on a copy of the site, test the important journeys, and only then apply the changes to the live site.

Yes. The Core Web Vitals are among the experience signals Google takes into account. More importantly, a fast site holds visitors better and converts better, which benefits both SEO and sales.

Yes. Our Care service takes over with tested updates, off-site backups, uptime and security monitoring, and performance tracking, so the site stays fast and safe over time.

An SEO audit is a full analysis of a site to identify what limits its visibility on Google: technical problems, indexing, speed, content quality, structure, links and competition. It ends in a prioritised action plan.

Analysis of indexing, technical health, Core Web Vitals, content, structure and internal linking, keywords and competition. The deliverable is an action plan ranked by impact and effort, presented in a meeting.

An online tool automatically detects visible technical problems, often without ranking them. An audit carried out by specialists checks every finding, analyses your content and your competitors, and turns it all into priorities that match your objectives.

Usually a few working days, depending on the size of the site, the number of languages and how deep the competitive analysis goes. The findings are then talked through in a meeting.

Ideally read access to Google Search Console and to your traffic analytics. That real data makes the audit far more precise than a crawl of the site alone.

Before a rebuild, after a drop in traffic or positions, when launching a new market or a new language, or simply when the site is not producing the enquiries you would expect despite good content.

It is the situation where several pages on the same site target the same query. Google hesitates between them, and none ranks as well as a single strong page would. The audit identifies those cases and proposes merging, differentiating or redirecting.

Yes, in most cases. Common causes are a rebuild with poor redirects, de-indexed pages, a technical problem, an algorithm update or a more relevant competitor. Search Console data lets the drop be dated and located.

If you would like us to. Because we also build sites, our teams can apply the technical and editorial corrections directly. The action plan nevertheless remains usable by your own team or another provider.

Yes, where your business depends on a geographic area. We then also examine your Google Business Profile, your reviews and the consistency of your information online.

A full audit is worthwhile before a rebuild, or once a year for an active site. Between audits, regular monitoring of positions, indexing and performance lets problems be spotted quickly.

It can be extended with a GEO component. We then check the access of the answer engines' crawlers, the clarity of your content, your structured data and what AI assistants already say about your company.

A GEO audit measures a company's visibility in the answers of generative AI engines such as ChatGPT, Gemini, Perplexity, Copilot and Google's AI Overviews, and then identifies the technical, editorial and off-site causes that explain its presence or its absence.

By asking it, repeatedly, the questions your customers would genuinely ask, and recording whether your company is mentioned, in what context and with which sources. A GEO audit does that in a structured way across several engines at once.

Chiefly ChatGPT, Google Gemini, Perplexity, Microsoft Copilot and Google's AI Overviews. The set can be adapted to the tools your customers actually use.

An SEO audit analyses your position in Google's ordinary results. A GEO audit measures whether you are cited in the answers generated by AI, and whether what is said is accurate. The two share foundations but do not measure the same thing.

They do, varying from one session and one wording to another. That is why the audit rests on a set of around thirty questions, asked under comparable conditions and measured again over time, so that dependable trends emerge rather than one-off results.

Find and correct the source of the error: outdated information on your site, an incomplete Google Business Profile, old directory entries or articles. The audit records those errors and indicates where to correct them first.

Often because they are described more clearly on their own site, mentioned on more reliable third-party sources, or answer the questions asked more directly. The audit compares those elements to identify the gap to close.

Usually a few working days, depending on the number of services, geographic areas and languages the question set has to cover. The findings are then talked through in a meeting.

Yes. AI assistants are increasingly used to find a provider nearby. For a local business the audit focuses particularly on the Google Business Profile, reviews and the consistency of local information.

It is an important advantage. Several answer engines rely partly on existing search indexes, such as those of Google and Bing. A site that is poorly indexed or technically fragile is less likely to be used as a source.

Yes. The question set defined during the audit serves as the baseline. It is measured again each month as part of our Visibility service, so the effect of the actions taken can be checked and priorities adjusted.

The audit provides the diagnosis and the action plan. The corrections can then be carried out by our teams, who cover development, SEO, content and structured data, or by your own team.