Technical friction
Broken pages, redirects, indexability constraints and performance issues created a weak starting point for efficient crawling and user experience.
How I worked on the technical, content and AI-search foundations of a Moroccan educational platform to make its value easier to discover, understand and measure.

Understanding the real business is the starting point of useful SEO strategy.

A screenshot is not available offline.
Open bewize.ma ↗Bewize is a Moroccan educational application offering interactive school support for children from CP to 6ème. It offers flashcards, quizzes, missions and progress tracking aligned with the Moroccan curriculum, covering Arabic, French, mathematics and English.
That creates multiple search audiences: parents looking for academic support, families comparing learning methods and schools researching education tools. My work was to connect these real needs to useful, accessible pages and build a stronger search-visibility foundation.
The company description reflects Bewize’s public website as reviewed in October 2026. The interface may change over time.
Google Search Console · Google Analytics 4 · Semrush · Performance audit tools
Technical SEO, content strategy, internal linking, competitive research and AI search readiness.
The task wasn't simply to publish more articles. First, I needed to identify what could prevent the site from being crawled, understood and surfaced to relevant searchers.
Broken pages, redirects, indexability constraints and performance issues created a weak starting point for efficient crawling and user experience.
Thin pages, inconsistent titles and descriptions and gaps between page topics and user intent created opportunities to improve relevance.
The education offer needed clearer structure and stronger information signals for AI search and answer-based discovery as well as classic organic results.
“My first priority was to understand what was holding visibility back — then organize the fixes by business impact, not by the size of the audit checklist.”
The initial project materials covered a sample of 31 pages and exposed structural, technical and content issues that informed prioritization.
Analyzed in the initial crawl; a subsequent audit covered approximately 100 pages. These are audit coverage figures, not growth KPIs.
| Area | What was detected | Why it mattered |
|---|---|---|
| Crawl & redirects | 404 errors and redirect paths | Can disrupt navigation and dilute efficient internal discovery. |
| Indexability | 5 of 31 pages not indexable | Important content may fail to enter search results. |
| Metadata | 9 duplicate meta descriptions; 9 overlong titles | Weaker differentiation and less compelling SERP messaging. |
| Thin content | 7 pages flagged for low word counts | Potential gaps in answering users' intent; word count alone isn't quality. |
| Mobile experience | Mobile performance score 52/100; LCP 10.2 seconds | Slower loading can frustrate mobile visitors. |
| Desktop experience | Desktop score 72/100 | Room for performance and layout improvements. |
| AI search readiness | AI Search Health 83%; linking score 91% | Tool-scored opportunities to clarify structure and relationships. |
Source: figures documented in the project audit and portfolio notes. Some metrics were produced by different tools at different moments; they are not a single controlled before/after experiment. The screenshots and report dates should be checked before external publication.
During the project, I worked across six complementary workstreams. The point was to build a logical sequence: diagnose, understand demand, optimize, then measure.
I examined Search Console and GA4 indicators to understand impressions, clicks, CTR, search queries and page performance before recommending changes.
I reviewed crawling, indexability, broken URLs, metadata, site structure, internal links and loading performance, separating blocking issues from lower-impact refinements.
Research translated how parents and schools search into a clearer content framework. The focus was matching useful information to the problems people actually describe.
I evaluated titles, descriptions, headings, page copy and contextual linking to make educational pages easier to interpret and more useful for readers.
I reviewed how the product, audience and educational topics could be presented more clearly for AI-powered discovery. This involved answer-friendly organization and consideration of structured data and entity signals.
I used an audit-first approach to track technical quality and evolving content health, with GSC and GA4 as the appropriate sources for traffic and behavior verification.
These comparisons come from the project’s reported audits. They describe tool-specific website-health scores, not a demonstrated increase in traffic, conversions or sales.
The reported comparisons suggest improved quality across performance, internal linking and the audit tool’s AI-readiness criteria. They are useful evidence of work on the website’s foundations.
They cannot independently demonstrate more Google clicks, higher keyword positions, more citations in AI assistants or additional business revenue.
Figures above reflect project audit comparisons provided during the portfolio-building work. Insert source screenshots with timestamps and obtain permission for client reporting before publishing externally.
Metadata and content improvements are more valuable when search engines can reliably reach and understand important pages.
For EdTech, the search language of parents, pupils and schools shapes where useful information should live.
Health scores reflect a particular evaluation tool. Sustainable SEO reporting also needs search and business outcomes over a defined period.
Bewize strengthened my approach to technical SEO, content mapping, internal linking and AI discovery analysis. I learned to connect audits to priorities and to distinguish technical progress from true business outcomes.

Whether you're losing rankings, need better local discovery, or want to prepare for AI search, we can start with a focused SEO assessment.