Website admin panel
ACCESS TO THE WEBSITE | Poland

CMS Access for SEO Work on Polish-Market Sites

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

Polish-market sites use a specific range of CMS platforms, hosting control panels, and admin configurations. This page covers what access looks like for Polish WordPress, Joomla, PrestaShop, and Shoper installations, how Polish 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 live in the CMS database or configuration files - they cannot be edited from outside the admin panel.

For Polish sites, several of these elements are located in positions specific to the CMS version and any installed Polish plugins:

• On Polish WordPress sites, SEO meta fields may be managed by Yoast SEO, Rank Math, or in some older Polish agency installations, All in One SEO Pack - each plugin stores meta data differently
• On Polish Joomla sites, meta data is stored per article in the Joomla database, and SEO-affecting configuration is in Global Configuration and the template settings
• On PrestaShop, title and meta description are managed per product and per category through the Metadata tab in the back office
• On Shoper, SEO fields are managed per product, per category, and in the Shoper SEO module settings

What We Access on Polish Sites

Page editor and content areas - to modify title tags, meta descriptions, H1, H2, H3 headings, and page body text for keyword optimization. For Polish-language pages, this includes ensuring keywords appear in their correct Polish grammatical form in the appropriate positions.

SEO plugin or built-in SEO fields - for the specific plugin or CMS field where Polish meta data is stored. On Polish WordPress sites, this is typically the Yoast SEO or Rank Math meta box. On Joomla, the article metadata fields and Global Configuration SEO settings. On PrestaShop, the Metadata tab per product/category.

Redirects manager - to correct redirect chains and loops identified in the audit. On Polish WordPress sites, this is typically the Redirection plugin or Rank Math's redirect module. On Polish Joomla sites, the built-in Joomla redirect component (accessible under Components → Redirect). On PrestaShop, the back office does not have a native redirect manager - redirect rules are implemented in the `.htaccess` file, which we access if hosting permits.

Robots.txt - if editable through the CMS or hosting panel. On Polish Joomla sites, `robots.txt` is a file in the site root - accessible via FTP or hosting file manager if not editable through Joomla admin. On Polish WordPress sites, it may be editable through Yoast SEO's tools.

Media library - to add or correct alt attributes on images. For PrestaShop, this is the product image alt field in each product record and the banner alt fields in the Positions module.

What We Do Not Access or Modify on Polish Sites

We do not access: payment gateways (Przelewy24, PayU, BLIK integrations on Polish e-commerce sites), customer order data, email accounts, hosting control panels (cPanel, DirectAdmin at home.pl, nazwa.pl, LH.pl), 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 menus (unless internal linking corrections are in scope), database tables beyond page content and SEO meta fields.

Every change we make is reversible. Title tags, meta descriptions, and alt attributes are text fields - reverting any of them takes seconds. The work report documents every change with before/after values.

How to Provide Access for Polish CMS Platforms

WordPress (Polish installations)

Administrator-level access is required. Editor-level access lacks permission to modify Yoast or Rank Math plugin settings or manage redirects.

What to send:

• Admin URL: `yoursite.pl/wp-admin/` (or custom admin URL if your Polish agency changed it for security)
• Username
• Password

Common complication on Polish WordPress sites: many Polish web agencies enable two-factor authentication (2FA) or change the default `/wp-admin/` URL as a security measure. If your site uses 2FA, create a separate Administrator account without 2FA for the duration of the package. Delete it after work is complete.

If your Polish WordPress site is hosted on home.pl's WordPress hosting tier (which uses a modified admin environment), confirm the admin URL format - home.pl WordPress hosting uses the standard `/wp-admin/` path.

Joomla (widely used in Poland)

Super User access is required. Standard Administrator access in Joomla may not have permission to modify Global Configuration (where SEF URL settings are located) or access the redirect component.

What to send:

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

Polish Joomla sites commonly use templates from Polish agencies (RocketTheme, TemplateMonster PL, or custom templates built by Polish developers). Some of these templates have SEO-relevant settings in the template manager (Template → Options) that require Super User access to modify.

PrestaShop (dominant in Polish e-commerce)

Back Office Administrator access is required. Employee accounts with restricted access may not have permission to edit product metadata, category metadata, or SEO configuration.

What to send:

• Back office URL: `yourstore.pl/admin-xxxx/` (PrestaShop randomizes the admin folder name for security - check your hosting file manager or email from your developer for the exact path)
• Email address (PrestaShop uses email as the login identifier)
• Password

PrestaShop-specific note: If your PrestaShop store was built or maintained by a Polish agency, the admin URL is typically in the format `/admin123456/` or similar randomized suffix. If you have lost the admin URL, it can be found in the `app/config/parameters.php` file (PrestaShop 1.7+) or via your hosting file manager.

Shoper (Polish-origin platform)

Shoper is a hosted e-commerce platform - unlike self-hosted CMSs, Shoper stores run on Shoper's infrastructure. This means there is no server-level access separate from the Shoper admin panel.

What to send:

• Admin URL: `yourstore.pl/admin/` (standard Shoper admin path)
• Login email and password

Note on Shoper hosting: Because Shoper is a SaaS platform, some technical fixes (redirect rules, custom cache configuration) are limited to what Shoper's admin panel exposes. Where server-level fixes are not possible through Shoper admin, we document the limitation and provide the exact settings to configure through Shoper's available SEO controls.

Other Polish CMS platforms

Polish websites also use: MODX (used by some Polish agencies), Drupal (used by Polish public sector and larger corporate sites), custom PHP CMSs built by Polish software houses, and Selly (Polish-origin platform for digital product sales). If your site runs on one of these, contact us before ordering to confirm access requirements and CMS compatibility.

Polish Hosting Control Panels

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

home.pl: Uses a proprietary control panel at `panel.home.pl`. For `.htaccess` access, the File Manager in the home.pl panel allows editing files in the site root. We do not need full panel access - if you can place specific `.htaccess` directives yourself, we provide the exact code.

nazwa.pl: Uses cPanel. File Manager in cPanel allows `.htaccess` editing. Alternatively, nazwa.pl hosting supports FTP access for `.htaccess` edits.

LH.pl: Uses DirectAdmin. File Manager in DirectAdmin allows file editing.

cyber_Folks (formerly Kylos): Uses cPanel or DirectAdmin depending on the hosting plan.

In all cases, we prefer to work with CMS-level admin access first. Hosting panel access is requested only when a specific fix requires it and when the fix cannot be implemented through the CMS. We document in advance which fixes require hosting panel access, and you can choose to implement those fixes yourself using our specifications rather than sharing hosting panel credentials.

How to Send Credentials Securely

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

Recommended methods for Polish clients:

Secure one-time note: Use privnote.com or onetimesecret.com - both are accessible without registration, generate a link that self-destructs after one view, and work reliably from Poland. Create one note per credential set (CMS login separate from hosting panel if both are needed).

Password manager share: If you use 1Password, Bitwarden, LastPass, or KeePass (widely used in Polish corporate environments), share a vault entry or create a shared folder specifically for this work.

Established secure channel: If we have established contact via a verified email thread or a messaging app you use for business communication (Telegram, WhatsApp), credentials sent there are acceptable. Avoid sharing credentials on public forums or in unverified channels.

After the work is complete, change your password immediately. If you created a separate account for our access, delete it from the CMS. For Joomla: Users → Manage → delete the account. For WordPress: Users → delete. For PrestaShop: Employees → delete employee record.

After the Work Is Complete

When you receive the work report, revoke access through whichever method is cleanest for your platform:

• Change the admin password for the account used during the package (applies to all platforms)
• Delete the separate account if you created one (recommended approach)
• For PrestaShop: check that the deleted employee record does not leave an active session

Clearing cache after access revocation: Polish WordPress sites using WP Rocket or W3 Total Cache should flush the cache after receiving the work report. Polish Joomla sites should clear Joomla's system cache (System → Clear Cache). PrestaShop has a cache clear function in Advanced Parameters → Performance. Clearing the cache ensures that optimized meta tags and title tags are served without delay from cached versions.

Frequently Asked Questions

Our WordPress site was built by a Polish agency that still manages it. Do we need their involvement? Only if you do not have direct admin access. You should have your own Administrator-level account on your site - this is good practice regardless of which agency built it. If the only admin account belongs to your agency, contact them to create a separate account for this work. You own your site's admin access.

The admin URL for our PrestaShop store was customized by our Polish developer. How do I find it? The admin folder name is visible in your hosting file manager. Log into your hosting control panel (cPanel at nazwa.pl, DirectAdmin at LH.pl, or home.pl's panel), navigate to File Manager, and look for a folder in your site's root directory that starts with "admin" followed by random characters. That is your PrestaShop back office URL.

Our Joomla site uses a two-factor authentication extension. What should we do? Create a new Super User account specifically for this work, without the 2FA extension applied to it. Most Polish Joomla 2FA extensions (including the popular TfaEmail or Akeeba LoginGuard) can be applied selectively per user. After the work is complete, delete the temporary account.

Can we give you FTP access instead of CMS admin access? CMS admin access is strongly preferred - changes applied through the admin panel trigger the CMS's own data validation and update mechanisms. FTP-level edits to PHP files or database exports are a backup approach for specific cases where CMS access is not available. If you can only provide FTP access, contact us before ordering to discuss feasibility for your specific platform.

What if we are uncomfortable sharing our hosting panel password? You do not need to share your full hosting panel credentials. For fixes that require `.htaccess` changes (redirect consolidation, cache headers), we provide the exact code to paste into the relevant file. You or your developer can implement those specific changes using your hosting panel without sharing the panel credentials with us.