← Back to all projects

Georgia Tours — Tour Booking, Payments & SEO Enhancements

A WordPress tour-booking website built around WP Travel Engine, with custom development focused on payment integration, international price presentation, trip-page UX, language selection, and search visibility. The work brings together booking-engine customization, theme-level layout changes, and SEO enhancements for a travel business promoting experiences in Georgia.

Project
Georgia Tours
My role
WordPress development, Payment integrations, custom plugin development, debugging, technical SEO
Year
2026
Platform
WordPress · WP Travel Engine · Tourex
Visit Georgia Tours
R&P Consulting homepage
Project context: a travel-booking experience for tours in Georgia.

The challenge

A tour website needs to do more than display attractive destinations. Visitors must be able to understand each trip, compare prices, choose a booking option, and move through checkout with confidence. Behind that experience, the site also needs reliable payment handling, consistent trip metadata, and a layout that makes the most important booking information easy to find.

The project involved extending an existing WordPress setup rather than replacing its booking engine. That meant working with WP Travel Engine's trip post type and hooks, the Tourex theme's templates, and Yoast SEO's existing metadata output without creating unnecessary conflicts or duplicate functionality.

A key constraint was to keep the booking system's actual transaction currency separate from any converted prices shown for convenience. Payment initiation, checkout display, and confirmed payment status had to remain distinct parts of the flow.

What I worked on

Flitt payment gateway integration

I built a plugin that allowed adding Flitt as a selectable payment method in the WP Travel Engine checkout, including gateway settings and the embedded-checkout flow.

The integration work included tracing order creation, checking credential configuration, and correcting the checkout-token endpoint used to open the payment interface.

From all this, the plugin also created bookings and sent the appropriate emails and notifications to the admin and clients who booked the trip.

Checkout request and response handling

Investigated the Create Order response and its signature verification logic. The implementation needs to validate each response according to the payment provider's contract rather than assume every response contains the same signature fields. A created order or opened checkout is not treated as proof of a successful payment.

Multi-currency price display planning

Created a display-only currency switcher plugin for GEL, USD, EUR, and GBP, using USD as the booking system's base currency.

The experience is intended to show indicative converted prices while clearly explaining that checkout continues to charge in the configured base currency.

Trip-page layout debugging

Traced the single-trip content flow through WP Travel Engine hooks and examined why the intended main-content-plus-sidebar layout was collapsing into one column.

The work focused on hook priorities and the surrounding theme/template structure instead of assuming that reordering callbacks alone would fix the layout.

SEO metadata and social sharing

Reviewed how Yoast SEO and the theme contribute trip titles, descriptions, and Open Graph metadata. The goal is to provide useful trip-specific snippets and sharing previews while avoiding duplicate tags from multiple layers of the WordPress stack.

FAQ content and structured data

Planned an FAQ structure using the ACF fieldsfaq_question and faq_answer, with corresponding FAQPage JSON-LD where appropriate.

Any generated schema matched the questions and answers visible on the page and avoided duplicating schema already emitted by other components.

Tour offer structured data

Evaluated the need for consistent Product/Offer-style structured data around tour pricing. The implementation reflected the actual offer and transaction currency, and accounted for the trip schema already available through the booking plugin before adding custom JSON-LD.

Theme and plugin integration

Worked within an existing WordPress stack rather than treating every requirement as a separate application.

The solution considers WP Travel Engine hooks, Tourex templates, Yoast output, ACF fields, and Elementor as connected parts of one visitor experience.

Booking experience

Trip details → booking → payment

01
Explore a tripDuration, itinerary and key facts
02
Review the priceClear base currency and display price
03
Choose paymentGateway selection in checkout
04
Confirm the outcomeBooking status follows verified payment state
Booking flow and payment-state considerations.
Technical SEO

Trip metadata built around the actual offer

TitleTrip name + destination
DescriptionDuration, location and booking context
FAQACF question-and-answer fields
OfferPrice and currency consistency
SEO and structured-data design considerations.

How it's built

Working with the WordPress booking engine

WP Travel Engine provides the core trip and booking functionality. The trip content type uses the trip slug, and the customization work builds around the plugin's existing hooks and data model. This approach keeps trip management within WordPress and reduces the need to recreate booking features that the plugin already provides.

The Tourex theme controls important parts of the presentation layer. When a trip page does not render in the intended layout, both the hook callbacks and the template's parent containers are used to creat the intended layout. Hook priority determines callback order but does not independently create a two-column layout or repair an incompatible wrapper.

Flitt checkout integration

The payment work separates order creation from the embedded checkout step and from final payment confirmation. The checkout flow uses the provider's token endpoint to initialize the embedded payment interface.

The token endpoint was distinguished from a separate checkout URL endpoint, and the Create Order response was reviewed against the signature checks applied by the integration.

A successful checkout initialization alone is not sufficient evidence that the live payment flow, callbacks, and booking-status updates are all working correctly, so I completed automated and manual end-to-end verification for those stages.

Currency display without changing the charge

The currency-switcher was built to be intentionally display-only. The planned currencies were Georgian lari (GEL), US dollars (USD), euros (EUR), and British pounds (GBP), with USD retained as the booking system's base currency. Frankfurter was used as the exchange-rate source, and the switcher was placed in the Elementor header as well as a custom footer section only show on mobile.

A modal was used to explain that converted values are indicative and that the final booking is charged in the base currency. This boundary matters because changing a display preference must never silently change the amount or currency sent to the payment gateway.

SEO, FAQs, and structured data

Yoast SEO was already participating in title and metadata generation, so custom SEO code needed to work with that output.

The FAQ implementation uses ACF fields named faq_question andfaq_answer. FAQPage JSON-LD was and ontinues to be generated from the same content users can see on the page.

Product/Offer-style schema also reflected the actual tour offer, including the correct price and currency. Since WP Travel Engine can emit trip-related schema, its existing output was inspected before custom structured data wass added. The aim was consistent, non-duplicated metadata rather than simply adding more JSON-LD.

Maintainability and debugging

The implementation uses WordPress-native extension points where possible, including plugin settings, hooks, filters, custom fields, and theme templates. PHP development tooling and WordPress/WP Travel Engine stubs were also part of the local workflow to improve editor completion and catch integration issues during development.

Project outcomes

Payment flowEmbedded checkout endpoint and response-validation during live payments.
Currency clarityA defined display-only conversion approach that keeps the base booking currency authoritative.
SEO foundationTrip metadata, ACF-powered FAQs, Open Graph, and structured-data requirements implemented.

Need a booking website or a custom WordPress integration?

I build and extend websites with a focus on reliable workflows, maintainable code, and a clear user experience.

Start a project

Frequently Asked Questions

Getting started
What information do you need from me to get started on a project?

I typically need a clear description of your project goals, target audience, any design preferences, technical requirements, and timeline expectations.

The more details you can provide, the better I can tailor my approach.

For larger projects, I'll provide a detailed questionnaire to help you articulate your vision.

I'm also happy to schedule an initial consultation call to discuss your needs more thoroughly.

Schedule a Consultation
Have you worked with businesses in my industry before?

I've worked with clients across diverse industries including healthcare, real estate, digital marketing, and others.

While each industry has unique requirements, my experience has taught me how to quickly adapt to different business domains.

For industries new to me, I invest time in research to understand your specific challenges and standards.

My portfolio includes examples of past work that demonstrate my versatility across sectors.

Contact Me
Project Planning and Execution
How do you prioritize features when working within budget constraints?

I use a value-driven approach to feature prioritization.

We'll collaborate to identify "must-have" versus "nice-to-have" features based on your business goals and user needs.

I will then implement core functionality first, then add enhancements as the budget allows. This approach ensures you get a functional product that delivers value, even with limited resources.

I'm transparent about what's achievable within your budget and can suggest phased implementations if needed. Please contact me to discuss this further

Contact Me
How long does a typical project take from start to finish?

Project timelines vary based on complexity and scope.

Simple websites typically take 1-2 weeks, while more complex web applications may require 1-3 months. E-commerce solutions generally take 1.5-3 months depending on customization needs.

After our initial consultation, I'll provide a detailed timeline with key milestones. I'm committed to meeting agreed-upon deadlines while maintaining quality standards.

How do you communicate progress throughout the development process?

I believe in transparent, consistent communication.

You'll receive weekly progress updates for longer projects and daily progress updates for shorter ones via email, and we'll have scheduled check-in calls at key milestones.

I also use project management tools that give you visibility into task completion and upcoming work. This approach ensures you're always in the loop.

For day-to-day communication, I'm available through your preferred channel (email, Discord, Slack, etc.). My goal is to keep you informed without overwhelming you with technical details unless neccessary.

Contact Me
Timelines and pricing
What is your pricing structure? Do you charge hourly, fixed-price, or use another model?

Add your typical timelines here, for example a custom theme in 3 to 5 weeks and a web application in 6 to 12.

How is pricing set?

I offer flexible pricing options tailored to your project needs:

  • Fixed-price contracts for well-defined projects with clear requirements
  • Hourly rates for exploratory work or projects with evolving scopes
  • Retainer arrangements for ongoing development needs

For most client projects, I prefer fixed-price agreements as they provide budget certainty.

After our initial consultation, I'll recommend the most appropriate pricing model and provide a detailed proposal.

All pricing options include regular milestones and deliverables to ensure transparency.

How do you handle change requests during a project?

I understand requirements can and do evolve as projects progress and minor adjustments are accommodated within the original agreement.

For substantial changes, I'll assess the impact on timeline and budget, then provide you with options before proceeding.

I document all change requests and maintain a change log that's accessible to you. This approach ensures transparency while allowing flexibility for your evolving needs.

Support and Maintenance
What is your availability for ongoing maintenance and support after project completion?

I offer several post-launch support options:

  • A 30-day warranty period for all projects to address any immediate issues
  • Monthly maintenance packages for regular updates and minor improvements
  • Priority support agreements for business-critical applications
  • Ad-hoc support at my standard hourly rate

I recommend discussing maintenance needs early in the project planning phase so we can build with long-term support in mind. My goal is to ensure your solution remains secure, performant, and up-to-date.

What's your process for handling urgent issues or emergency fixes?

For clients with support agreements, I provide a dedicated channel for reporting urgent issues with guaranteed response times (typically within 1-4 hours depending on your support tier).

For clients without support agreements, you can contact me at anytime and we will schedule a time to discuss the issue. My availability is flexible and I'll do my best to respond within one business day.

Do you offer any guarantees or warranties on your work?

Yes, all my work comes with a 30-day warranty period after project completion. During this time, I'll fix any bugs or issues at no additional cost.

I also guarantee:

  • Code that follows industry best practices
  • Cross-browser compatibility as specified in our agreement
  • Responsive design for mobile devices
  • Adherence to accessibility guidelines
  • Secure coding practices

My contracts clearly outline what's covered under warranty and what would constitute billable changes or enhancements. Contact me if you need further clarification or have a question about these guarantees.

Contact Me

Let's work together

Tell me what you're building and I'll reply with next steps.