Website admin panel
ACCESS TO THE WEBSITE

CMS Access for SEO Work on Ukrainian-Market Sites

Before any SEO optimization work begins, we need login access to your site's content management system. This is a requirement for every package - SEO optimization involves making direct changes in the CMS, and those changes cannot be applied without credentials.

Ukrainian-market sites use a specific set of CMS platforms and hosting environments that differ from Western European markets. This page explains what access looks like for Ukrainian WordPress, Joomla, 1C-Bitrix, and OpenCart installations, how Ukrainian hosting environments affect the access process, and how to provide credentials securely.

Why CMS Access Is Required

SEO optimization modifies specific elements on each page: title tags, meta descriptions, heading tags, image alt attributes, canonical tags, and redirect rules. These elements are stored in the CMS database or in CMS configuration files - they cannot be edited from outside the admin panel without the risk of introducing errors.

For Ukrainian sites, these elements are located in CMS-specific positions:

• On Ukrainian WordPress sites with WPML or TranslatePress, meta data for Ukrainian and Russian language versions is managed through language-specific interfaces that require admin-level access to reach
• On 1C-Bitrix, SEO meta fields are stored in information block element properties and in Bitrix's section properties - separate from the page content, requiring admin-level navigation to the correct component settings
• On Ukrainian Joomla sites, meta data is in the article metadata tab and in Joomla's Global Configuration - both require Super User level access
• On Ukrainian OpenCart, SEO data is in the SEO tab of each product and category record in the admin panel

We apply changes directly in these fields rather than providing a list of recommendations, because precision matters: a misplaced character in a canonical URL or a language code error in an hreflang tag produces the opposite of the intended result.

What We Access on Ukrainian Sites

Page editor and content areas - to modify title tags, meta descriptions, H1, H2, H3 headings, and page body text for keyword inclusion. For Ukrainian-language pages, this means applying keywords in their correct Ukrainian grammatical form. For Russian-language Ukrainian-market pages, this means applying Russian-language Ukrainian-market keyword forms. For en-UA pages, English content with Ukrainian market context.

SEO plugin or built-in SEO fields - for the specific plugin or CMS interface where meta data is stored:

• WordPress: Yoast SEO or Rank Math meta box in the post/page editor; for WPML sites, the language-specific meta fields in each language version
• Joomla: Article metadata tab (Title, Description, Keywords fields) and Global Configuration for SEO settings
• Bitrix: Element properties in the information block admin, section SEO properties, and Bitrix's built-in SEO module settings
• OpenCart: SEO tab in product edit and category edit sections; meta tag fields in information pages

Redirects manager - to correct redirect chains and loops identified in the audit. On WordPress, this is the Redirection plugin or Rank Math's redirect module. On Joomla, the Joomla Redirect Manager (Components → Redirect). On Bitrix, redirects are managed through the Bitrix admin's URL Rewriting section or through `.htaccess` rules on the server. On OpenCart, redirects are managed in the OpenCart URL Aliases table or via `.htaccess`.

robots.txt - if editable through the CMS. On WordPress, via Yoast SEO's robots.txt editor. On Bitrix, the `robots.txt` file is in the site root - accessible via Bitrix's File Manager in the admin panel or via FTP. On Joomla and OpenCart, `robots.txt` is also in the site root and accessible via hosting file manager or FTP if not editable through the CMS.

Media library / image management - to add or correct alt attributes on images. For Bitrix, image alt fields are in the element properties for each information block element. For OpenCart, product images have alt fields in the product edit tab.

What We Do Not Access or Modify on Ukrainian Sites

We do not access: payment processing systems (Liqpay, Wayforpay, Portmone integrations on Ukrainian e-commerce sites), customer and order data, user account databases, email accounts, hosting control panels, FTP/SFTP, or server-level configurations beyond what is necessary for specific documented fixes.

We do not modify: page templates or themes, CSS or PHP files, plugin configurations unrelated to SEO, navigation structure (unless internal linking corrections are in the package scope), Bitrix information block structure or component configurations beyond meta fields, OpenCart product pricing or inventory data.

All changes we make are reversible. Meta fields and text content can be restored to their previous state in seconds. The work report documents every change with before/after values.

How to Provide Access for Ukrainian CMS Platforms

WordPress (Ukrainian installations, often with WPML or TranslatePress)

Administrator-level access is required. Editor-level access does not have permission to modify Yoast or Rank Math plugin settings, manage redirects, or access WPML's translation management for all language versions.

What to send:

• Admin URL: `yoursite.ua/wp-admin/` (or the custom admin URL if your Ukrainian web studio changed the default path)
• Username
• Password

For Ukrainian WordPress sites with WPML: confirm that the Administrator account we use has access to all language versions in WPML's Translation Management - some WPML configurations restrict language access per user role. Check WPML → Translation Management → translators configuration.

For sites with two-factor authentication enabled (increasingly common on Ukrainian business WordPress sites after security incidents): create a separate Administrator account without 2FA for the duration of the package. Delete it after the work is complete.

Joomla (used by Ukrainian web agencies)

Super User access is required. Standard Administrator access in Joomla may not permit modification of Global Configuration SEO settings or access to the full Joomla redirect component.

What to send:

• Admin URL: `yoursite.ua/administrator/`
• Username
• Password

Ukrainian Joomla sites often have Russian-language or Ukrainian-language admin interfaces. This does not affect our workflow - we navigate Joomla's admin structure the same way regardless of interface language.

1C-Bitrix (widely used by Ukrainian medium and large businesses)

Administrator access is required. Bitrix's role-based access system has granular permissions - ensure the account provided has access to: Information Blocks (edit mode), SEO module, File Manager (for robots.txt and .htaccess access), and the Redirect Rules section if Bitrix's URL rewriting module is in use.

What to send:

• Admin URL: `yoursite.ua/bitrix/admin/` (standard Bitrix admin path)
• Login (email or username)
• Password

Bitrix-specific notes:

• Bitrix composite mode: If your Bitrix site uses composite caching (a Bitrix speed optimization feature), meta tag changes in the admin panel will not appear in the served HTML until the composite cache is cleared. We document this as a step to take after optimization and can provide instructions for clearing it.
• Bitrix OTP (one-time password): Some Ukrainian corporate Bitrix installations use OTP-based two-factor authentication. If yours does, ask your Bitrix administrator to create a separate admin account without OTP for the duration of the package.
• Bitrix SaaS (Bitrix24): If your site is built on Bitrix24 (the cloud version), rather than a self-hosted 1C-Bitrix site, the admin access path and the available SEO fields differ. Contact us before ordering to confirm compatibility.

OpenCart (Ukrainian e-commerce)

Administrator access via the OpenCart admin panel.

What to send:

• Admin URL: `yourstore.ua/admin/` (standard OpenCart admin path)
• Username
• Password

For OpenCart stores where the admin folder has been renamed for security (a common practice recommended by Ukrainian hosting providers): the renamed admin folder is accessible via the path your Ukrainian developer used during setup. Check your developer documentation or hosting file manager if you have forgotten the path.

Custom Ukrainian CMS platforms

Some Ukrainian businesses use CMS platforms built by Ukrainian software houses - custom PHP frameworks, custom e-commerce systems, or hybrid systems built on Ukrainian hosting infrastructure. If your site uses a custom CMS, contact us before ordering. We confirm access requirements and feasibility based on what fields are available in your specific system's admin interface.

Ukrainian Hosting Control Panel Access

For fixes that require server-level access - primarily `.htaccess` redirect rules and browser caching headers - we may need access to your hosting control panel in addition to the CMS. Ukrainian hosting providers use:

Hosting.ua: Uses cPanel on most plans. File Manager in cPanel allows `.htaccess` editing and file management. Hosting.ua also supports FTP access.

Deltahost: Uses cPanel or DirectAdmin depending on the plan tier. `.htaccess` editing is available through the File Manager.

Mirohost: Uses a proprietary control panel and cPanel on different plan tiers. File access is available through File Manager. Mirohost shared hosting has `.htaccess` restrictions on some older plan configurations - if a specific directive is blocked, we provide alternative implementation approaches.

Freehost.com.ua: Uses cPanel. File Manager is available. Note that free-tier Freehost accounts have limited `.htaccess` override permissions - some redirect and cache header configurations are not applicable on free Freehost hosting.

Ukrtelekom (UTELS) hosting: Uses DirectAdmin or cPanel depending on the data center and plan. `.htaccess` editing is available through File Manager.

International hosting used by Ukrainian clients (Hetzner, OVH, AWS, DigitalOcean): These follow standard Linux server conventions. `.htaccess` is editable via SSH, file manager, or the hosting control panel. We provide exact code for any `.htaccess` changes needed.

In all cases, we prefer CMS-level admin access first. Hosting panel access is requested only for specific documented fixes. You can choose to implement hosting-level fixes yourself using the specifications we provide, rather than sharing hosting panel credentials.

How to Send Credentials Securely

Do not send login credentials in plain email or standard messaging apps.

Recommended for Ukrainian clients:

Privnote (privnote.com) and OneTimeSecret (onetimesecret.com): Both are available without registration, generate a link that self-destructs after one view, and work reliably from Ukraine. Create a separate note for each credential set.

Password manager share: If you use Bitwarden (open source, widely used in Ukrainian IT companies), 1Password, or KeePass (common in Ukrainian corporate environments), share a vault item or temporary shared folder for the duration of the package.

Established communication channel: If contact has been established via a specific email thread or verified business messaging channel, credentials sent there are acceptable. Avoid sharing credentials on public platforms, social media, or unverified channels.

After the work is complete, change your password immediately. If you created a separate account for our access, delete it:

• WordPress: Users → delete the account
• Joomla: Users → Manage → delete the account
• Bitrix: Settings → Users → deactivate or delete the account
• OpenCart: System → Users → delete

Frequently Asked Questions

Our Bitrix site was built and is maintained by a Ukrainian web studio. Do we need their involvement? Only if you do not have your own Administrator access to the Bitrix admin panel. You should have independent admin access to your own site - this is important regardless of which agency built it. If the only admin account belongs to the web studio, ask them to create a separate admin account for this work. Providing access to your own site should not require the web studio's ongoing involvement.

We use Bitrix24 (cloud version) rather than self-hosted Bitrix. Is that compatible? Bitrix24 and self-hosted 1C-Bitrix have different admin interfaces and different locations for SEO-relevant fields. Bitrix24's CRM-focused interface does not expose the same information block SEO properties as self-hosted Bitrix. Contact us before ordering with your specific Bitrix24 configuration - we will confirm which elements are accessible and what the package can cover.

Our Ukrainian OpenCart installation has multiple language versions (Ukrainian, Russian, English). Do we need to provide anything special? No special preparation is needed. OpenCart's multilingual product and category meta fields are accessible through the standard admin panel under the same product/category edit screens - each language version has its own meta tab. Confirm that the Administrator account we use has access to all language versions in OpenCart's language settings.

Can we provide FTP access instead of CMS admin access for our Ukrainian Joomla site? CMS admin access is strongly preferred. Joomla's article meta fields and configuration are stored in the database - editing them via FTP would require direct database access rather than file editing. If CMS admin access is unavailable, we can discuss an alternative approach using database export/import for specific fields, but this adds time and requires technical capability on your side. Contact us before ordering if this is your situation.

What if we are uncomfortable providing our main Bitrix admin credentials? Create a separate Bitrix Administrator account specifically for this work. In Bitrix: Settings → Users → Add new user → assign Administrator role. Provide the credentials for that account, and deactivate or delete it after the work report is delivered. This is the cleanest approach from a security standpoint and requires no sharing of your primary admin credentials.

How long does it take to set up access for a Ukrainian site? For a standard Ukrainian WordPress, Joomla, or OpenCart site, providing access credentials takes 5-10 minutes. For a Bitrix site where you need to create a new admin account or locate the Bitrix admin URL, allow 15-20 minutes. The package timeline begins when we confirm receipt of working credentials. Any delay in providing access delays the start of work proportionally.