AEM SEO Implementation | Community
Skip to main content
AEM_Forum
AEM_Forum
Level 10
June 18, 2017
Solved

AEM SEO Implementation

  • June 18, 2017
  • 11 replies
  • 21514 views

Hi all,

Let us say I have two teams, one for UI development (HTML, JS and CSS)  and the other for AEM Development and the work for these two teams is clearly delineated.

For SEO Implementation:

1. it looks like most of the work needs to be done by UI development team. Is it true?

2. Configuring the Rich Text Editor for producing accessible content:

Is it the job of UI development team?

3. What is the work of AEM Development team?

4. I read configuring components for Alt Txt etc. This definitely is the work of AEM Development team.

5. So, how to estimate AEM efforts?

6. Could we say 5% of effort for all components for configuring Alt Txt etc?

7. What is the difference among levels A, AA and AAA from the implementation perspective?

Does it have any bearing on AEM efforts?

Appreciate all your replies.

Thanks,

Rama.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by ogill

    Hi Rama,

    take two requirements, URL structure, in order to enforce this, you would instruct your authors in how they should structure the site and name their pages.

    Adding an H1 to every page. The design team creates the the HTML outputted, the AEM team creates the components to allow the author to enter the title, they then add the H1 component to the template so it is available every time a page is created from the template.

    Your question is very open ended and more suited to consulting. If you have a specific use case and need help implementing it, then that would be a more appropriate question. No harm in asking, but open ended questions don't always get an answer

    Regards,

    Opkar

    11 replies

    Show previous replies
    T
    Talha223
    February 11, 2024

    Hi Rama,

    Thanks for your questions regarding SEO implementation and the roles of UI development and AEM development teams. Let's break it down:

    1. For SEO implementation:

      • Yes, indeed, a significant portion of the work for SEO implementation typically falls under the purview of the UI development team. This includes optimizing HTML structure, implementing structured data markup, and ensuring proper usage of headings and tags for improved search engine visibility.

    2. Configuring the Rich Text Editor for producing accessible content:

      • While configuring the Rich Text Editor for accessibility is primarily a UI development task, collaboration with the AEM development team may be necessary to integrate custom features or functionalities to enhance accessibility standards.

    3. The work of AEM Development team:

      • The AEM development team is responsible for the backend development and configuration of the Adobe Experience Manager (AEM) platform. This includes creating and configuring components, templates, and workflows to support content management and delivery.

    4. Configuring components for Alt Text, etc.:

      • Correct, configuring components for attributes like Alt Text is typically handled by the AEM development team, as it involves backend configuration within the AEM platform to ensure accessibility standards are met.

    5. Estimating AEM efforts:

      • Estimating AEM efforts involves considering factors such as the complexity of the website or application, the number of custom components required, integration with third-party systems, and the level of customization needed for SEO optimization and accessibility.

    6. Effort allocation for configuring Alt Text, etc.:

      • While it's challenging to assign a specific percentage of effort for configuring Alt Text and other accessibility features, it's essential to consider these requirements during the estimation process and allocate resources accordingly based on project needs.

    7. Difference among levels A, AA, and AAA from the implementation perspective:

      • The levels A, AA, and AAA refer to the WCAG (Web Content Accessibility Guidelines) standards for accessibility. While all levels aim to improve accessibility, each level has progressively stricter criteria. From an implementation perspective, adhering to higher WCAG levels may require additional effort and resources, potentially impacting AEM development efforts.

    In conclusion, collaboration between the UI development and AEM development teams is key to successful SEO implementation and accessibility. By leveraging the strengths of both teams and considering SEO and accessibility requirements from the outset, you can boost your SEO and digital PR campaign while ensuring an inclusive and accessible user experience.

    Hope this helps clarify things for you!

    Best regards,

    Terms & ConditionsAccessibility statement

    Loading footer...