Wordpress
Special Mail Tags for Submissions
[_remote_ip] — This tag is replaced by the submitter’s IP address.
[_user_agent] — This tag is replaced by the submitter’s user agent (browser) information.
[_url] — This tag is replaced by the URL of the page in which the contact form is placed.
[_date] — This tag is replaced by the date of the submission.
[_time] — This tag is replaced by the time of the submission.
[_invalid_fields] — This tag is replaced by the number of form fields with invalid input.
[_serial_number] — This tag is replaced by a numeric string whose value increments, so this tag can work as the serial number of each submission. Requires Flamingo 1.5+ be installed.
Post-Related Special Mail Tags
These special mail-tags provide information about the post that contains the contact form.
Be aware that these [_post_*] tags work only when the contact form is placed inside post content. In cases where the contact form is outside of post content, such as when the contact form is placed in a sidebar widget or embedded in a theme’s template file, a blank text will replace the tag.
[_post_id] — This tag is replaced by the ID of the post.
[_post_name] — This tag is replaced by the name (slug) of the post.
[_post_title] — This tag is replaced by the title of the post.
[_post_url] — This tag is replaced by the permalink URL of the post.
[_post_author] — This tag is replaced by the author name of the post.
[_post_author_email] — This tag is replaced by the author email of the post.
Site-Related Special Mail Tags
These special mail-tags provide information about the WordPress website on which you manage the contact forms. You’ll find them especially useful when you want to reuse the same set of contact form templates between many websites, because you are freed from manual modification of the site information for each website.
[_site_title] — This tag is replaced by the title of the website.
[_site_description] — This tag is replaced by the description (tagline) of the website.
[_site_url] — This tag is replaced by the home URL of the website.
[_site_admin_email] — This tag is replaced by the email address of the primary admin user of the website.
User-Related Special Mail Tags
These special mail-tags provide information about the current logged-in user.
Since these [_user_*] tags work only when the submitter has an account on the WordPress site and is logged in, it is recommended to turn on the subscribers-only mode setting anytime you use these tags.
If you want to use these tags but don’t want to use the subscribers-only mode, explicitly turn on the nonce setting. Otherwise, the logged-in user data will be reset by the WP REST API, and a blank text will replace the tag.
[_user_login] — This tag is replaced by the login name of the user.
[_user_email] — This tag is replaced by the email address of the user.
[_user_url] — This tag is replaced by the website URL of the user.
[_user_first_name] — This tag is replaced by the first name of the user.
[_user_last_name] — This tag is replaced by the last name of the user.
[_user_nickname] — This tag is replaced by the nickname of the user.
[_user_display_name] — This tag is replaced by the display name of the user.
FAQ
Common questions about WordPress project work and ongoing support.
What kinds of WordPress sites do you work with?
I work with business WordPress sites, WooCommerce stores, and projects that need to grow step by step — without unnecessary complexity or fragile solutions. This includes both new launches and existing sites that need refinements, support, or careful technical updates.
Can you improve an existing site without a full redesign?
Yes. Most tasks involve sites that are already live: new sections, functional improvements, WooCommerce changes, performance optimisation, or technical fixes. The goal is for the site to stay stable, manageable, and easy to develop further.
What types of tasks do you take on most often?
Most often this is custom WordPress development, Figma design implementation, WooCommerce refinements, support for live sites, fixing technical issues, and practical improvements over time. In selected scenarios I also help with light AI automations for content, enquiries, or internal admin workflows.
Do you work on WordPress speed and performance?
Yes. WordPress optimisation usually involves reviewing the theme, plugins, images, fonts, page structure, and the site's overall technical neatness. The aim is not a "magic button", but practical changes that make the site faster and easier to maintain.
Do you use AI when working on WordPress sites?
Yes, but only where it genuinely helps the process. AI works best for content drafts, FAQ or support assistants, enquiry handling, and small automations around an existing WordPress site. The approach is simple: AI should reduce routine work, not complicate the site.
What do I need to prepare to discuss a task or project?
Usually a short description of the site, the task, the desired outcome, and examples or technical constraints if you have them is enough. If the project is already live, it also helps to share the current site or a staging environment — this makes it easier to understand the scope of work.
Can I get in touch not for a new site, but for support or specific improvements?
Yes. I work not only on new builds, but also on live sites that need to be maintained, fixed, and improved gradually. This can include new pages, admin changes, WooCommerce refinements, small UX improvements, or technical maintenance.
Need help with a WordPress project?
If you need custom WordPress development, design implementation, or support for an existing site, I would be happy to review the project.