skapator

Element Bits adds a growing collection of lightweight, easy-to-use widgets to Elementor page builder, helping you build beautiful pages faster.
Custom Widgets
EB Heading: Flexible heading with sub-text and divider options.
EB Google Map: Embed Google Maps with custom markers and styling.
EB Swiper Arrow: Standalone previous/next arrows for any Swiper slider.
<h3>External services</h3>
This plugin loads the Google Maps JavaScript API (<code>https://maps.googleapis.com/maps/api/js</code>) whenever a page displays the EB Google Map widget or block.
<ul>
<li>Purpose – the script is required to draw the map and place the marker at the latitude/longitude you configure. </li>
<li>When it runs – we enqueue the script only on front-end requests that actually contain the map widget. </li>
<li>Data sent to Google – the visitor’s browser requests the file from Google’s CDN, transmitting the IP address and standard browser headers. If you enable the widget’s “Detect my position” option, the browser will first ask the visitor’s permission to share its precise location; no geolocation data is sent unless the visitor consents. </li>
<li>Provider – Google LLC. See the <a href="https://cloud.google.com/maps-platform/terms" rel="nofollow ugc">Google Maps Platform Terms of Service</a> and the <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a>.</li>
</ul>

Element Bits

Element Bits adds a growing collection of lightweight, easy-to-use widgets to Elementor page builder, helping you build beautiful pages faster.

Weston Ruter

This plugin is developed at 
<a href="http://www.shepherd-interactive.com/" title="Shepherd Interactive
specializes in web design and development in Portland, Oregon">Shepherd 
Interactive</a> for the benefit of the community. No support is available. 
Please post any questions to the <a href="https://wordpress.org/tags/override-post-title-with-first-content-heading?forum_id=10" rel="ugc">support 
forum</a>.
On a singular post/page, normally in The Loop <code>the_title()</code> returns 
 post_title; if, however, this needs to be overridden so that a 
custom content heading is displayed (i.e. for SEO purposes), then an 
 h1 or <code>h2</code> element may be supplied at the beginning of 
the <code>post_content</code> and the contents of this heading element 
will be returned by <code>the_title()</code> instead of <code>post_title</code>.
From a technical perspective, the site title in the main header should be 
an <code>h1</code> element and the page/post title should in an <code>h2</code> 
element within an <code>article</code>, <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#headings-and-sections" rel="nofollow ugc">per HTML5</a>:
<blockquote>Sections may contain headings of any rank, but authors are strongly 
encouraged to either use only `h1` elements, or to use elements of the 
appropriate rank for the section’s nesting level.</blockquote>
This is seen in the default WordPress theme and the HTML specifications. However, 
SEO places higher priority on the contents of an <code>h1</code> element, so if 
every page of a site has the exact same <code>h1</code> contents (the site name), 
then search engines may not be as likely to rank the page based on the unique 
contents of the <code>h2</code>. It has been <a href="http://blogsessive.com/blogging-tips/blog-seo-tips-titles/" rel="nofollow ugc">suggested</a> 
therefore that the <code>h1</code> and the <code>h2</code> elements be swapped, 
so that the site title appears in an <code>h2</code> and so that the unique page 
title appears in the <code>h1</code>. While the specifications don’t prefer this 
arrangement, it is not incorrect, also per HTML5:
<blockquote>Both of the documents are semantically identical and would produce the same 
outline in compliant user agents.</blockquote>
So if different heading levels are semantically equivalent, and if search 
engines really place that much importance on <code>h1</code>, then SEO wins.
In both cases, content section headings should be coded with <code>h3</code> and 
below.
Technical note: If the <code>$post</code> object is not passed into <code>the_title</code> 
filter, then the page’s <code>the_title()</code> must be called before every other 
 the_title() call <code>in_the_loop()</code>

Override Post Title with First Content Heading

On a singular post/page, returns the contents of the first content H1 or H2 instead of the post_title as normally. Facilitates SEO.

Element Bits vs Override Post Title with First Content Heading