Recommended Posts

As a web developer I always want to improve the search results of my websites in popular search engines. Because of that I find the topic of structured data very interesting and want to learn more about them. Recently I tried out a few of the ways how to provide more information to a website and want to share my solutions. Most of the structured data can be included directly in the markup or as JSON-LD at the end of your document (right before the closing body tag). I prefer the last one, because I don't like to have bloated HTML markup.

Breadcrumbs

Breadcrumbs are an alternative way to show the your page hierarchy inside search results, instead of showing just the plain URL. Just like the breadcrumbs on a website. Following the example, I ended up with this code:

<?php if(strlen($page->parents()) > 0) { ?>
	<!-- Breadcrumbs -->
	<script type="application/ld+json">
		{
			"@context": "http://schema.org",
			"@type": "BreadcrumbList",
			"itemListElement": [
				<?php

					$positionCounter = 1;
					$separator = ',';

					foreach($page->parents() as $parent) {

						if($parent->id == $page->parents()->last()->id) {
							$separator = '';
						}

						echo '
								{
									"@type": "ListItem",
									"position": "' . $positionCounter . '",
									"item": {
										"@id": "' . $parent->httpUrl . '",
										"name": "' . $parent->title . '"
									}
								}' . $separator . '
							';

						$positionCounter++;

					}

				?>
			]
		}
	</script>
<?php } ?>

First I am checking if the page has parents, then I follow the follow the markup of the example. I save the position of each parent in the variable positionCounter and increase its amount after each loop. As a last step I tried to end the JSON objects by not include the separating comma after the last object. This is why I am using the separator variable.

Site name and sitelinks searchbox

Using JSON-LD you can provide an alternative site name and a sitelinks searchbox inside the search results (Inception :lol: ).

<!-- WebSite -->
<script type="application/ld+json">
	{
		"@context": "http://schema.org",
		"@type": "WebSite",
		"name" : "Your site name",
		"alternateName" : "Your alternative site name",
		"url": "<?= $pages->get(1)->httpUrl ?>",
		"potentialAction": {
			"@type": "SearchAction",
			"target": "<?= $pages->get(1)->httpUrl ?>search/?q={search_term_string}",
			"query-input": "required name=search_term_string"
		}
	}
</script>

I am not 100% sure, if the sitelinks searchbox works this way. Maybe someone who made this work before could confirm it, that would help me out.  ;)

Organization

For organizations you could provide a logo and links to your social profiles.

<!-- Organization -->
<script type="application/ld+json">
	{
		"@context": "http://schema.org",
		"@type" : "Organization",
		"name" : "Your organization name",
		"url" : "<?= $pages->get(1)->httpUrl ?>",
		"logo": "<?= $pages->get(1)->httpUrl ?>site/templates/images/logo.png",
		"sameAs" : [
			"https://www.facebook.com/your-organization-url",
			"https://www.instagram.com/your-organization-url/" // All your social profiles
		]
	}
</script>

This one I think is self explanatory.

Article

If you have an blog or a news site you could enhance your articles with structured data with an thumbnail and author.

<?php if($page->template == "post") { ?>
	<!-- Article -->
	<script type="application/ld+json">
		{
			"@context": "http://schema.org",
			"@type": "NewsArticle",
			"mainEntityOfPage": {
				"@type": "WebPage",
				"@id": "<?= $page->httpUrl ?>"
			},
			"headline": "<?= $page->title ?>",
			"image": {
				"@type": "ImageObject",
				"url": "<?= $page->thumbnail->httpUrl ?>", // Image field in template
				"height": <?= $page->thumbnail->height ?>,
				"width": <?= $page->thumbnail->width ?>
			},
			"datePublished": "<?= date('c', $page->created) ?>",
			"dateModified": "<?= date('c', $page->modified) ?>",
			"author": {
				"@type": "Person",
				"name": "<?= $page->createdUser->first_name . ' ' . $page->createdUser->last_name ?>" // Text fields added to core module ProcessProfile
			},
			"publisher": {
				"@type": "Organization",
				"name": "Your organization name",
				"logo": {
					"@type": "ImageObject",
					"url": "<?= $pages->get(1)->httpUrl ?>site/templates/images/logo.png",
					"width": 244, // Width of your logo
					"height": 36 // Height of your logo
				}
			},
			"description": "<?= $page->summary ?>" // Text field in template
		}
	</script>
<?php } ?>

Here I am enabling structured data for the template called post. I also have the text fields first_name and last_name added to the core module ProcessProfile, the image field thumbnail and the text field summary added to the template.

Just a small note: I know you could use $config->httpHost instead of $pages->get(1)->httpUrl, but I found the second one more flexibel for changing environments where you have for example HTTPS enabled.

Those are the structured data I have in use so far. I hope I haven't made a mistake, at least the testing tool doesn't complain. But if you find something, please let me know. I love how easy it is with ProcessWire to get all the information from various pages and use them in this context.

As mentioned above, I am nowhere an expert with structured data, but maybe some of you would like to provide also some examples in this thread.  ;)

Regards, Andreas

  • Like 11

Share this post


Link to post
Share on other sites

I can certainly see the intent, but I'm always cringing when I see something like that. A website is first and foremost for users and I'm not really seeing why the user should download 1.5 times the size of data, just to have lot's of (duplicate) content appended in a only machine readable format. In my mind, if it should be machine readable then supply an api to do so. It might seem verbose, but I'm more in favor of something like h-card, which is just wrapping around existing content. 

But in the end I'm also the one being quite glad about hardly working in the hell of SEO :)

  • Like 2

Share this post


Link to post
Share on other sites

That is a valid point and after all structured data are completely optional. There are a lot of trends, like the recent AMP project of Google for example, where I am thinking likewise, but as developer you sometimes have to make compromises to increase your audience.  ;)

Share this post


Link to post
Share on other sites

I'm doing all my structured data with helper functions, and for most sites i will have around 5-6 schema.org types.

I have found that this is a major benefit for SEO, and for search results accuracy in general.

Not to mention that some other 'competing' CMSs provide some structured data plugins or out-of-the box generated markup, and while it is generated automatically and therefore not always totally accurate, it has been shown to give some of those sites an edge on search rankings, and placement in things like google events, or news.

  • Like 1

Share this post


Link to post
Share on other sites

I'm starting to add some structured data to sites too, where relevant, to see what sort of impact it does have on search results.

From a technical perspective though, I'd highly recommend using json_encode() over generating strings.

Here's one I made earlier (very simple):
 

<?php
$socialLinks = array(
    'facebook' => 'https://www.facebook.com/BestPageEver',
);

$ldJson = array(
	'@context' => 'http://schema.org',
	'@type' => 'Organization',
	'name' => $homepage->title,
	'url' => $homepage->httpUrl,
	'sameAs' => array(),
);

foreach ($socialLinks as $name => $url) {
	$ldJson['sameAs'][] = $url;
}
?>

<script type="application/ld+json">
<?= json_encode($ldJson, JSON_PRETTY_PRINT); ?>
</script>
  • Like 6

Share this post


Link to post
Share on other sites

Always great to read someone elses approach.

Personally, I never noticed much of an SEO benefit from rich snippets and structured data but it was very early days when I first started evaluating them. At the time they were a new format and were considered to be a minor ranking signal to Google.

I did read (somewhere) just this week that Google are about to give structured data much more weight as a ranking signal but can't find the article now. Will post here if I can locate it.

Share this post


Link to post
Share on other sites

@Macrura:

Exactly that is the reason, why I want to dig deeper into this topic. I also noticed, that some WordPress themes for example provide a basic support for structured data. But mostly they are not very accurate and assume a lot of the data or generalize them. Luckily with the API of ProcessWire you have complete control of your data you want to use.

If you have some examples you would like to share, feel free to do so. The main purpose of this thread was to see if some of you also want to share your experience with structured data.  ;)

@Peter Knight:

The benefit I noticed so far is that the search results provide more information (especially with breadcrumbs). But I don't have them in use for very long and Google takes its time to update their indexes, although they are fast compared to other search engines. So time will tell the difference.

If you ever remember the article you have read, I would be interested in a link.

@Craig A Rodway:

Thank you for the hint. Using json_encode() is much more elegant than my original solution. I updated my code and you can see it below. This time I haven't separated my code into sections. Also there are probably still some thinks I can improve.

<?php

	$homeUrl = $pages->get(1)->httpUrl;

	// Organization
	$organization = array(
		"@context" => "http://schema.org",
		"@type" => "Organization",
		"name" => "Your organization name",
		"url" => $homeUrl,
		"logo"=> "{$homeUrl}site/templates/images/logo.png",
		"sameAs" => [
			"https://www.facebook.com/your-organization-url",
			"https://www.instagram.com/your-organization-url/"
		]
	);

	// WebSite
	$website = array(
		"@context" => "http://schema.org",
		"@type" => "WebSite",
		"name" => "Your site name",
		"alternateName" => "Your alternative site name",
		"url" => $homeUrl,
		"potentialAction" => [
			"@type" => "SearchAction",
			"target" => "{$homeUrl}search/?q={search_term_string}",
			"query-input" => "required name=search_term_string"
		]
	);

	// Breadcrumbs
	$breadcrumbs;

	if(strlen($page->parents()) > 0) {

		$listItems = array();
		$positionCounter = 1;

		foreach($page->parents() as $parent) {

			$listItems[] = [
				"@type" => "ListItem",
				"position" => $positionCounter,
				"item" => [
					"@id" => $parent->httpUrl,
					"name" => $parent->title
				]
			];

			$positionCounter++;

		}

		$breadcrumbs = array(
			"@context" => "http://schema.org",
			"@type" => "BreadcrumbList",
			"itemListElement" => $listItems
		);

	}

	// Article
	if($page->template == "post") {

		$article = array(
			"@context" => "http://schema.org",
			"@type" => "NewsArticle",
			"mainEntityOfPage" => [
				"@type" => "WebPage",
				"@id" => $page->httpUrl
			],
			"headline" => $page->title,
			"image" => [
				"@type" => "ImageObject",
				"url" => $page->thumbnail->httpUrl,
				"height" => $page->thumbnail->height,
				"width" => $page->thumbnail->width
			],
			"datePublished" => date('c', $page->created),
			"dateModified" => date('c', $page->modified),
			"author" => [
				"@type" => "Person",
				"name" => "{$page->createdUser->first_name} {$page->createdUser->last_name}"
			],
			"publisher" => [
				"@type" => "Organization",
				"name" => "Your organization name",
				"logo" => [
					"@type" => "ImageObject",
					"url" => "{$homeUrl}site/templates/images/logo.png",
					"width" => 244,
					"height" => 36
				]
			],
			"description" => $page->summary
		);
	}

?>

		<!-- Schema -->

		<!-- Organization -->
		<script type="application/ld+json">
			<?= json_encode($organization, JSON_PRETTY_PRINT); ?>
		</script>

		<!-- WebSite -->
		<script type="application/ld+json">
			<?= json_encode($website, JSON_PRETTY_PRINT); ?>
		</script>

<?php if(strlen($page->parents()) > 0) { ?>
		<!-- Breadcrumbs -->
		<script type="application/ld+json">
			<?= json_encode($breadcrumbs, JSON_PRETTY_PRINT); ?>
		</script>
<?php } ?>

<?php if($page->template == "post") { ?>
		<!-- Article -->
		<script type="application/ld+json">
			<?= json_encode($article, JSON_PRETTY_PRINT); ?>
		</script>
<?php } ?>

Regards, Andreas

  • Like 1

Share this post


Link to post
Share on other sites

sure, here are some examples, i have these in a file called schema_helpers.php, which is in my shared functions folder:

1.)


function siteSchema() {

	$page = wire('page');

	$schema = array(
		"@context" 			=> "http://schema.org",
		"@type"				=> "Website",
		"url"				=> wire('pages')->get(1)->httpUrl,
		"name"				=> $page->title,
		"description"		=> '',
		"potentialAction" 	=> array(
			"@type"			=> "SearchAction",
			"target" 		=> wire('pages')->get(1000)->httpUrl . "?q={search_term}",
			"query-input" 	=> "required name=search_term"
		),
		"about"				=> array(
			"@type" 		=> "Thing",
			"name"			=> "A very interesting THING",
			"description" 	=> "Website about a very interesting THING"
		)
	);

	if($page->summary) {
		$schema['description'] = $page->summary;
	} else {
		unset($schema['description']);
	}

	return '<script type="application/ld+json">' . json_encode($schema) . '</script>';

}

2.) News

function jsonldNews($item, $settings) {

	$image = $item->image ?: getFallbackImage($item);
	if(!$image) return;

	$out = '';
	$jsonld = array();

	$jsonld["@context"] 		= "http://schema.org/";
	$jsonld["@type"] 			= "NewsArticle";
	$jsonld["name"] 			= $item->title;
	$jsonld["headline"] 		= $item->title;
	$jsonld["url"] 				= $item->httpUrl;
	$jsonld["mainEntityOfPage"] = array(
			'@type' => "WebPage",
			'@id'	=> $item->httpUrl
			);
	$jsonld["description"]		= $item->summary;
	$jsonld["datePublished"]	= date(DATE_ISO8601, $item->published);
	$jsonld["dateModified"]		= date(DATE_ISO8601, $item->modified);
	$jsonld["dateline"]	        = date(DATE_ISO8601, strtotime($item->news_date));
	$jsonld["wordCount"]		= str_word_count($item->body);
	$jsonld['author']		= $settings['author'];
	$jsonld['publisher']		= $settings['entity'];
	$jsonld['articleBody']		= $item->body;
	$jsonld['articleSection']	= $item->categories_select->first()->title;

	// Publisher
	$pubLogo = wire('pages')->get(3525)->image;
	if($pubLogo) {
		$pubLogo = $pubLogo->height(60);

		$jsonld['publisher']		= array(
			'@type'	=>'Organization',
			'name'	=> 'A Publisher',
			'url'	=> 'https://publisher.org/',
			'logo'	=> array (
				'@type' 	=> 'ImageObject',
				'url' 		=> $pubLogo->httpUrl,
				'height' 	=> $pubLogo->height,
				'width'		=> $pubLogo->width
			)
		);
	}

	// News Items may have a featured image
	$image = $image->width(696);
	$jsonld['image']		= array(
		"@type" => "ImageObject",
		'url'	=> $image->httpUrl,
		'height'=> $image->height,
		'width' => $image->width
	);

	$out .= '<script type="application/ld+json">' . json_encode($jsonld) . '</script>';

	return $out;
}

3.) Event

function jsonldEvent($event) {

	if(!$event->event_location_select) return;

	if($event->template == 'event-child') {
		// inherit unset fields needed
		$event->event_link 				= $event->event_link ? : $event->parent->event_link;
		$event->body 					= $event->body ? : $event->parent->body;
		$event->event_location_select 	= $event->event_location_select ? : $event->parent->event_location_select;
		$event->price					= $event->price ? : $event->parent->price;
		$event->currency_code			= $event->currency_code ? : $event->parent->currency_code;
		$event->link					= $event->link ? : $event->parent->link;
	}

	$out = '';

	foreach($event->event_date_m as $ed) {

		$jsonld = array();

		$date8601 = date(DATE_ISO8601, strtotime($ed));

		$jsonld["@context"] 	= "http://schema.org/";
		$jsonld["@type"] 		= "MusicEvent";
		$jsonld["name"] 		= $event->title;
		$jsonld["url"] 			= $event->event_link;
		$jsonld["description"]	= $event->body;
		$jsonld["startDate"]	= $date8601;

		if($event->event_location_select) {
			$state = $event->event_location_select->state ? $event->event_location_select->state->title : $event->event_location_select->address_state;

			$jsonld["location"] = array(
				"@type" 	=> "Place",
				"name"		=> $event->event_location_select->title,
				"url"		=> $event->event_location_select->link,
				"address" => array(
				  "@type" 			=> "PostalAddress",
				  "streetAddress" 	=> $event->event_location_select->address_street,
				  "addressLocality" => $event->event_location_select->address_city,
				  "addressRegion" 	=> $state,
				  "postalCode" 		=> $event->event_location_select->address_zip,
				  "addressCountry" 	=> $event->event_location_select->country->title
				)
			);
		}

		if($event->price && $event->currency_code && $event->link) {
			$jsonld["offers"] = array(
				"@type" 		=> "Offer",
				"description" 	=> "Tickets",
				"price"			=> $event->price,
				"priceCurrency" => $event->currency_code,
				"url"			=> $event->link
			);
		}

		$out .= '<script type="application/ld+json">' . json_encode($jsonld) . '</script>';
	}

	return $out;
}

Also - I don't think you need to use JSON_PRETTY_PRINT

  • Like 5

Share this post


Link to post
Share on other sites

Also - I don't think you need to use JSON_PRETTY_PRINT

It's not necessary at all. I just find it handy when debugging to see the output in a more human-readable way :)

Thanks for sharing your examples.

Share this post


Link to post
Share on other sites

I also would like to thank you for sharing your examples. Wrapping the data blocks in helper functions is smart. There is much I can learn from.  :)

It's not necessary at all. I just find it handy when debugging to see the output in a more human-readable way :)

 That was also the reason I let JSON_PRETTY_PRINT enabled. The final JSON-LD is in my case minified with ProCache.

Share this post


Link to post
Share on other sites

I always use the google testing tool anyway to see how the data is being read, so i never even look at the source code (lol)

Share this post


Link to post
Share on other sites

You mean the one Facebook is providing? If so I am not quiet following how open graphs are related to structured data?

I used so far the testing tool from Google. But for developing I had most of the time the source code directly opened to check if everything is looking the right way.

Share this post


Link to post
Share on other sites

Hi Guys, First thank you for sharing your knowledge!  These post help me a lot! 


I have also created a separate php file, but I have a doubt because from manuals should be inserted in the <head> and I have just include the php file inside it. But if I think well it in the web inspector I have never seen any code referring to the Structured Data like <script type="application/ld+json">.  Why this? OK, maybe I may not have seen enough sites, but I can not find even on well-known sites.

Could be a great if I use a js file and adding this?  
or I see many site have only the google tag manager link. Do you think the google tool are better and is enough?

  • Like 1

Share this post


Link to post
Share on other sites

@AndZyk Did the breadcrumbs + searchbox feature actually work with your client site(s)?

Today I was reading the official Google docs, but when I search for pinterest (searchbox example) or the book example for breadcrumbs) I don't see those things.

I even fired up different browsers or went into incognito mode, but still nothing.

Google is well-known for throwing out features and tools, just to neglect them soon afterwards.

If these things have been shut down, I'm not going to bother with the extra effort, or even going to advertise such features as a "nice-to-have" SEO add-on.

Share this post


Link to post
Share on other sites

Hello @MarcoPLY,

I am glad this post helped you.

On 5/4/2018 at 11:34 AM, MarcoPLY said:

But if I think well it in the web inspector I have never seen any code referring to the Structured Data like <script type="application/ld+json">.  Why this? OK, maybe I may not have seen enough sites, but I can not find even on well-known sites.

JSON-LD is the recommended format for structured data. JSON-LD is JSON for Linked Data.

Adding structured data with JSON-LD inside <body> is still valid, but usually it is placed inside <head> for better separation. Most of search engine specific code goes inside <head>.

On 5/4/2018 at 11:34 AM, MarcoPLY said:

Could be a great if I use a js file and adding this?  

You could try the jsonld.js preprocessor, but I think it would be easier just to use PHP, since that is the easiest way to get data from ProcessWire.

On 5/4/2018 at 11:34 AM, MarcoPLY said:

or I see many site have only the google tag manager link. Do you think the google tool are better and is enough?

As far as I know is Google Tag Manager a different tool. Google Tag Manager is great for example online shops, where you want to track the customer experience. It seems to be an analytics tool for internal analytics, but has probably no effect on search results. But I have never used Google tag manager, just watched a few videos, so I could be wrong.

 

Hello @dragan,

21 hours ago, dragan said:

Did the breadcrumbs + searchbox feature actually work with your client site(s)?

Breadrcumbs has worked for me, although it is not very useful on websites with only one parent-page. 😀

Searchbox, Organization and Article hasn't worked for me. 🙁

21 hours ago, dragan said:

Google is well-known for throwing out features and tools, just to neglect them soon afterwards.

If these things have been shut down, I'm not going to bother with the extra effort, or even going to advertise such features as a "nice-to-have" SEO add-on.

I don't think they will neglect structured data, but the support seems to be lacking.

On Google I/O 2017 for example they announced upgrades to the Structured Data Testing Tool, but the upgrade doesn't seem to be available yet.

In my opinion I am not that convinced of structured data compared to the time I have wrote this post. The extra effort is not that time consuming, but the results are a little bit disappointing. So I can totally understand if you don't want to bother with it. 😉

Regards, Andreas

  • Like 2

Share this post


Link to post
Share on other sites

Thanks for your feedback @AndZyk. Well, what do you know - I'll be attending a full-day Google Analytics workshop @ Google Zurich end of May. I'm going to ask Google staff if they know more about structured data (though chances are, they will be giving me the usual runaround... "that's another department, ask there"). I also actually gave feedback on those two doc pages, but who knows who will read this - and if they're going to bother editing / clarifying the docs.

  • Like 2

Share this post


Link to post
Share on other sites
16 hours ago, AndZyk said:

In my opinion I am not that convinced of structured data compared to the time I have wrote this post. The extra effort is not that time consuming, but the results are a little bit disappointing.

My opinion on JSON-LD markup is the total opposite. It works really well for my (testing) sites and for clients.
By now we talk about 30+ sites so finding are quite solid in my opion.

There are a few things I noticed when working with JSON-LD or any other kind of meta-data/rich-snippets.

Organization

Implementation: easy
Results: may vary
Finding: better results when used together with Google Business and when there is a good amount of BRANDED queries

Product

Implementation: medium
Results: Rich snippets in search results with pricings, stock infos, much higher CTR
Finding: takes up to a week for the first results to show up

Review

Implementation: medium
Results: rich snippets like Product but with additional rating stars, CTR even slightly better
Finding: takes up to a week for the first results to show up

Breadcrumbs

Implementation: easy
Results: may vary - larger sites benefit from it way better than small sites and one-pager
Finding: don't try to trick Google - use the same data as on the page (same title, same url, same everything) otherwise pages can drop or can disappear

Site search

Implementation: easy
Results: may vary when sites are too small
Finding: the bigger the site, the more products it containts, the more "BRAND PRODUCT/CONTENT" queries Google notices the more likely Google will place a site search in search results - working example: https://www.otto.de/ (not one of my clients)

Article

Implementation: easy
Results: may vary
Finding: works well for recent news, breaking news - not so working well on old or outdated posts and small blogs/sites.

Recipes

Implementation: medium
Results: huge snippets, high CTR
Finding: you should be one of the very first with that recipe otherwise your snippet will not show up

Events

Implementation: medium
Results: may vary in many ways - sometimes you get a nice event list under your site, sometimes your events show up for totally different queries that belong some how to your event (listed on event sites or for that very special location)
Finding: it's a good idea to create JSON-LD for events as the results can spread across the web for all kinds of search queries - perfect for events you want to see everywhere on not just for your site/your brand.

  • Like 2

Share this post


Link to post
Share on other sites

@wbmnfktr I do not have the same amount of sites as feedback but I think like you. Specially for the products or whatever if you sell something have a Rich snippets is so important. I think this is more the a Implementation: medium. Everything grow your CTR just a bit must definitely use it!

I don't know if you never use but how use the Review and aggregateRating ? This could be important to increase product reliability and trust in the site, and for what I know (i never try) if link Google Business the review will be connected to the specific product and show up on the google page and in the snippets you can see the yellow star if it's using the aggregateRating tag.  But I don't really feel to add the Review directly inside the Structured Data. What you think about?

 

 

Share this post


Link to post
Share on other sites
2 minutes ago, MarcoPLY said:

Implementation: medium

It depends on the products you work with. Clothing can be super work-intensive but by now all products and data I had to work with were easy to implement in JSON-LD as everything exists in that special ProcessWire page. So we can say: medium to lots-of-work in this case.

2 minutes ago, MarcoPLY said:

Review and aggregateRating

I use whatever is possible. I had sites/products were no real ratings existed so we left them out. Faking reviews or ratings should be avoided. Google will find out about those sneaky tricks. They did in the past, the will in the future. The star ratings are a fantasic CTR booster. Combined with some more on-page work in title and description you can boost the results even more.

When there are real reviews for a product then test it. Take one product, add the review(s) and check the results every 2 days for at least 6 weeks. 

A little side-note: changing existing pages and adding JSON-LD can bring your results down for a short period of time. At least did we notice these changes with some projects. Since then we update only small chunks of product pages at a time. Within 4 weeks those sites sometimes drop 3 to 10 places but come back much stronger and stay.

Google Business and Reviews ... I guess you think of Search Console by Google. There are tools in it that help Google and your site with Rich data. Google Business can help you with things like Local SEO, Social SEO and citations. If you or your client can see a good amount of Branded queries you shouldn't only consider Google Business you have to take care of that.

 

  • Like 1

Share this post


Link to post
Share on other sites

yes @wbmnfktr is true, some time to make a completely schema can mean a lot of work! With pw is possible to create on the template an excellent base that is already enough!

I agree with you about the Reviews, I will wait at the moment and test it later with some really reviews when we will have. The thing about the star ratings is that you can not have if you don't have any review. 

About the Google Business yes was the one for the local seo, this also can work like a reference page. But you're right, I checked better and is not in correlation with the Structured Data. It's better use for other way. Instead the Search Console could be connected.

Thank you! also for the note it's very good to know!! I will test it.

Share this post


Link to post
Share on other sites
On 5/7/2018 at 9:17 AM, wbmnfktr said:

My opinion on JSON-LD markup is the total opposite. It works really well for my (testing) sites and for clients.
By now we talk about 30+ sites so finding are quite solid in my opion.

Hello @wbmnfktr,

maybe I will give Structured Data another chance. I haven't tried anymore than I wrote in my initial post.

You seem to be really experienced with Structured Data. If you have some examples or code snippets you would like to share, I think many people would appreciate it. 😉

Regards, Andreas

Share this post


Link to post
Share on other sites

You definitely should give them another try @AndZyk. Since your first post a lot of things changed.

Am I really experienced? Maybe kind of. Ask me this when I finished the next 100 projects with lots of rich snippets/schema-markup. 😉

My examples and code snippets wouldn't be any different than any other resource out there.
I really love this tool: https://technicalseo.com/seo-tools/schema-markup-generator/

You can create several kinds of markup as an example and implement them in your project.
Those examples are a great starting point for everything. From breadcrumb to review or events

Test your markup over at Google and do what they want you to optimize in your markuphttps://search.google.com/structured-data/testing-tool/u/0/

Check the schema.org definitions and guides for more details: http://schema.org/

Set up Google Search Console, check your markup with it and let Google crawl your optimized sites. Get reportings on errors and fix them fast.

As written before:

  1. start with small parts of site (if possible)
  2. check results every 2 days for several weeks
  3. don't try to trick Google
  4. don't fake reviews
  5. don't fake review-counts or anything else

If you are into Local SEO do the basics and create company and localBusiness markup with everything you can (logo, social profiles, site search, opening hours, ...), connect to Google My Business.

Feel free to contact me or ask whatever you want. It's easier for me to answer a question right now. 

 

  • Like 3

Share this post


Link to post
Share on other sites

Hi @wbmnfktr, Thank you for the web tool it's great.

I have made the json-dl file and this work well, I can see a reach snipper with valuation, price, availability. There are all the info I put except for the photo. I use the same code I use in the header  page->image_card and in the header work well that give me the correct url. But in the schema give me a different url, this one: \/site\/assets\/files\/1059\/nome.jpg .  I don't know why, the description work well: $page->Description. Maybe the problem isn't here. How I can show also the photo of the product? 

Thank you!

Share this post


Link to post
Share on other sites

Are you using a module or a self-generated JSON-LD snippet?

Where do you see the result (Google Testing, Browser extension, ...)?

It shouldn't matter but you want to use httpUrl for JSON-LD.

 

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Noel Boss
      Page Query Boss
      Build complex nested queries containing multiple fields and pages and return an array or JSON. This is useful to fetch data for SPA and PWA.
      You can use the Module to transform a ProcessWire Page or PageArray – even RepeaterMatrixPageArrays – into an array or JSON. Queries can be nested and contain closures as callback functions. Some field-types are transformed automatically, like Pageimages or MapMarker.
      Installation
      Via ProcessWire Backend
      It is recommended to install the Module via the ProcessWire admin "Modules" > "Site" > "Add New" > "Add Module from Directory" using the PageQueryBoss class name.
      Manually
      Download the files from Github or the ProcessWire repository: https://modules.processwire.com/modules/page-query-builder/
      Copy all of the files for this module into /site/modules/PageQueryBoss/ Go to “Modules > Refresh” in your admin, and then click “install” for the this module. Module Methods
      There are two main methods:
      Return query as JSON
      $page->pageQueryJson($query); Return query as Array
      $page->pageQueryArray($query); Building the query
      The query can contain key and value pairs, or only keys. It can be nested and 
      contain closures for dynamic values. To illustrate a short example:
      // simple query: $query = [ 'height', 'floors', ]; $pages->find('template=skyscraper')->pageQueryJson($query); Queries can be nested, contain page names, template names or contain functions and ProcessWire selectors:
      // simple query: $query = [ 'height', 'floors', 'images', // < some fileds contain default sub-queries to return data 'files' => [ // but you can also overrdide these defaults: 'filename' 'ext', 'url', ], // Assuming there are child pages with the architec template, or a // field name with a page relation to architects 'architect' => [ // sub-query 'name', 'email' ], // queries can contain closure functions that return dynamic content 'querytime' => function($parent){ return "Query for $parent->title was built ".time(); } ]; $pages->find('template=skyscraper')->pageQueryJson($query); Keys:
      A single fieldname; height or floors or architects 
      The Module can handle the following fields:
      Strings, Dates, Integer… any default one-dimensional value Page references Pageimages Pagefiles PageArray MapMarker FieldtypeFunctional A template name; skyscraper or city
      Name of a child page (page.child.name=pagename); my-page-name A ProcessWire selector; template=building, floors>=25
      A new name for the returned index passed by a # delimiter:
      // the field skyscraper will be renamed to "building": $query = ["skyscraper`#building`"]  
      Key value pars:
      Any of the keys above (1-5) with an new nested sub-query array:
      $query = [ 'skyscraper' => [ 'height', 'floors' ], 'architect' => [ 'title', 'email' ], ]  
      A named key and a closure function to process and return a query. The closure gets the parent object as argument:
      $query = [ 'architecs' => function($parent) { $architects = $parent->find('template=architect'); return $architects->arrayQuery(['name', 'email']); // or return $architects->explode('name, email'); } ] Real life example:
      $query = [ 'title', 'subtitle', // naming the key invitation 'template=Invitation, limit=1#invitation' => [ 'title', 'subtitle', 'body', ], // returns global speakers and local ones... 'speakers' => function($page){ $speakers = $page->speaker_relation; $speakers = $speakers->prepend(wire('pages')->find('template=Speaker, global=1, sort=-id')); // build a query of the speakers with return $speakers->arrayQuery([ 'title#name', // rename title field to name 'subtitle#ministry', // rename subtitle field to ministry 'links' => [ 'linklabel#label', // rename linklabel field to minlabelistry 'link' ], ]); }, 'Program' => [ // Child Pages with template=Program 'title', 'summary', 'start' => function($parent){ // calculate the startdate from timetables return $parent->children->first->date; }, 'end' => function($parent){ // calculate the endate from timetables return $parent->children->last->date; }, 'Timetable' => [ 'date', // date 'timetable#entry'=> [ 'time#start', // time 'time_until#end', // time 'subtitle#description', // entry title ], ], ], // ProcessWire selector, selecting children > name result "location" 'template=Location, limit=1#location' => [ 'title#city', // summary title field to city 'body', 'country', 'venue', 'summary#address', // rename summary field to address 'link#tickets', // rename ticket link 'map', // Mapmarker field, automatically transformed 'images', 'infos#categories' => [ // repeater matrix! > rename to categories 'title#name', // rename title field to name 'entries' => [ // nested repeater matrix! 'title', 'body' ] ], ], ]; if ($input->urlSegment1 === 'json') { header('Content-type: application/json'); echo $page->pageQueryJson($query); exit(); } Module default settings
      The modules settings are public. They can be directly modified, for example:
      $modules->get('PageQueryBoss')->debug = true; $modules->get('PageQueryBoss')->defaults = []; // reset all defaults Default queries for fields:
      Some field-types or templates come with default selectors, like Pageimages etc. These are the default queries:
      // Access and modify default queries: $modules->get('PageQueryBoss')->defaults['queries'] … public $defaults = [ 'queries' => [ 'Pageimages' => [ 'basename', 'url', 'httpUrl', 'description', 'ext', 'focus', ], 'Pagefiles' => [ 'basename', 'url', 'httpUrl', 'description', 'ext', 'filesize', 'filesizeStr', 'hash', ], 'MapMarker' => [ 'lat', 'lng', 'zoom', 'address', ], 'User' => [ 'name', 'email', ], ], ]; These defaults will only be used if there is no nested sub-query for the respective type. If you query a field with complex data and do not provide a sub-query, it will be transformed accordingly:
      $page->pageQueryArry(['images']); // returns something like this 'images' => [ 'basename', 'url', 'httpUrl', 'description', 'ext', 'focus'=> [ 'top', 'left', 'zoom', 'default', 'str', ] ]; You can always provide your own sub-query, so the defaults will not be used:
      $page->pageQueryArry([ 'images' => [ 'filename', 'description' ], ]); Overriding default queries:
      You can also override the defaults, for example
      $modules->get('PageQueryBoss')->defaults['queries']['Pageimages'] = [ 'basename', 'url', 'description', ]; Index of nested elements
      The index for nested elements can be adjusted. This is also done with defaults. There are 3 possibilities:
      Nested by name (default) Nested by ID Nested by numerical index Named index (default):
      This is the default setting. If you have a field that contains sub-items, the name will be the key in the results:
      // example $pagesByName = [ 'page-1-name' => [ 'title' => "Page one title", 'name' => 'page-1-name', ], 'page-2-name' => [ 'title' => "Page two title", 'name' => 'page-2-name', ] ] ID based index:
      If an object is listed in $defaults['index-id'] the id will be the key in the results. Currently, no items are listed as defaults for id-based index:
      // Set pages to get ID based index: $modules->get('PageQueryBoss')->defaults['index-id']['Page']; // Example return array: $pagesById = [ 123 => [ 'title' => "Page one title", 'name' => 123, ], 124 => [ 'title' => "Page two title", 'name' => 124, ] ] Number based index
      By default, a couple of fields are transformed automatically to contain numbered indexes:
      // objects or template names that should use numerical indexes for children instead of names $defaults['index-n'] => [ 'Pageimage', 'Pagefile', 'RepeaterMatrixPage', ]; // example $images = [ 0 => [ 'filename' => "image1.jpg", ], 1 => [ 'filename' => "image2.jpg", ] ] Tipp: When you remove the key 'Pageimage' from $defaults['index-n'], the index will again be name-based.
       
      Help-fill closures & tipps:
      These are few helpfill closure functions you might want to use or could help as a
      starting point for your own (let me know if you have your own):

      Get an overview of languages:
          $query = ['languages' => function($page){         $ar = [];         $l=0;         foreach (wire('languages') as $language) {             // build the json url with segment 1             $ar[$l]['url']= $page->localHttpUrl($language).wire('input')->urlSegment1;             $ar[$l]['name'] = $language->name == 'default' ? 'en' : $language->name;             $ar[$l]['title'] = $language->getLanguageValue($language, 'title');             $ar[$l]['active'] = $language->id == wire('user')->language->id;             $l++;         }         return $ar;     }]; Get county info from ContinentsAndCountries Module
      Using the [ContinentsAndCountries Module](https://modules.processwire.com/modules/continents-and-countries/) you can extract iso
      code and names for countries:
          $query = ['country' => function($page){         $c = wire('modules')->get('ContinentsAndCountries')->findBy('countries', array('name', 'iso', 'code'),['code' =>$page->country]);         return count($c) ? (array) $c[count($c)-1] : null;     }]; Custom strings from a RepeaterTable for interface
      Using a RepeaterMatrix you can create template string for your frontend. This is
      usefull for buttons, labels etc. The following code uses a repeater with the
      name `strings` has a `key` and a `body` field, the returned array contains the `key` field as,
      you guess, keys and the `body` field as values:
          // build custom translations     $query = ['strings' => function($page){         return array_column($page->get('strings')->each(['key', 'body']), 'body', 'key');     }]; Multilanguage with default language fallback
      Using the following setup you can handle multilanguage and return your default
      language if the requested language does not exist. The url is composed like so:
      `page/path/{language}/{content-type}` for example: `api/icf/zurich/conference/2019/de/json`
       
          // get contenttype and language (or default language if not exists)     $lang = wire('languages')->get($input->urlSegment1);     if(!$lang instanceof Nullpage){         $user->language = $lang;     } else {         $lang = $user->language;     }     // contenttype segment 2 or 1 if language not present     $contenttype = $input->urlSegment2 ? $input->urlSegment2 : $input->urlSegment1;     if ($contenttype === 'json') {         header('Content-type: application/json');         echo $page->pageQueryJson($query);         exit();     } Debug
      The module respects wire('config')->debug. It integrates with TracyDebug. You can override it like so:
      // turns on debug output no mather what: $modules->get('PageQueryBoss')->debug = true; Todos
      Make defaults configurable via Backend. How could that be done in style with the default queries?
      Module in alpha Stage: Subject to change
      This module is in alpha stage … Query behaviour (especially selecting child-templates, renaming, naming etc)  could change
    • By FrancisChung
      Hi, I have an ongoing issue with Google SEO that I can't seem to fix. Wondering if anyone has come across a similar situation?

      We deployed a new version of the website using a new deployment methodology and unfortunately, the wrong robots.txt file was deployed basically telling Googlebot not to scrape the site.

      The end result is that if our target keywords are used for a (Google) search, our website is displayed on the search page with "No information is available for this page." 

      Google provides a link to fix this situation on the search listing, but so far everything I have tried in it hasn't fixed the situation.
      I was wondering if anyone has gone through this scenario and what was the steps to remedy it?
      Or perhaps it has worked and I have misunderstood how it works?

      The steps I have tried in the Google Webmaster Tool :
      Gone through all crawl errors Restored the Robots.txt file and Verified with Robots.txt tester Fetch/Fetch and Render as Google as both Desktop/Mobile, using root URL and other URLs, using Indexing Requested / Indexing Requested for URL and Linked Pages. Uploaded a new Sitemap.xml  Particularly on the Sitemap page, it says 584 submitted, 94 indexed.
       
      Would the Search Engine return "No Information available" because the page is not indexed? The pages I'm searching for are our 2 most popular keywords and entry points into site. It's also one of 2 most popular category pages.  So I'm thinking it probably isn't the case but ...

      How can I prove / disprove the category pages are being indexed?

      The site in questions is Sprachspielspass.de. The keywords to search are fingerspiele and kindergedichte.

       
    • By Krlos
      Hi, I'm using Formbuilder to build forms in my  website, I have different forms to track Google Adwords Conversions but I have like 20 differents forms.
      I was wondering how do you guys handle conversions in Google Adwords
    • By Noel Boss
      » A more exhaustive version of this article is also available on Medium in English and German «
      First, we'd like to thank the very helpful community here for the excellent support.
      In many cases we found guidance or even finished solutions for our problems.
      So a big THANK YOU!!!
       
      We are pleased to introduce you to the new Ladies Lounge 18 website. The next ICF Women’s Conference will take place in Zurich and several satellite locations across Europe. We embarked on bold new directions for the development of the website — in line with the BRAVE theme.

      Ladies Lounge 18 — ICF Woman’s Conference website on Processwire ICF Church is a European Church Movement that started 20 years ago in Zurich and since experienced tremendous growth. There are already well over 60 ICF churches across Europe and Asia. ICF is a non-denominational church with a biblical foundation that was born out of the vision to build a dynamic, tangible church that is right at the heartbeat of time.
      With the growth of the Ladies Lounge from a single-site event to a multi-site event, the demands and challenges to the website have also increased. A simple HTML website no longer cuts it.
      Simplified frontend Our goal with the development of the new site was it to present the different locations — with different languages and partly different content — under once uniform umbrella — while at the same time minimising the administrative effort. In addition to the new bold look and feel, this year’s website is now simpler and easier and the information is accessible with fewer clicks. 
      Some highlights of the new website
      Thanks to processwire, all contents are maintained in one place only, even if they are displayed several times on the website 100% customised data model for content creators Content can be edited directly inline with a double-click:  

      Multi-language in the frontend and backend Dynamic Rights: Editors can edit their locations in all available languages and the other content only in their own language Easy login with Google account via OAuth2 Plugin Uikit Frontend with SCSS built using PW internal features (find of files…) Custom Frontend Setup with Layout, Components, Partials and Snippets Only about 3 weeks development time from 0 to 100 (never having published a PW before) Despite multi-location multi-language requirement, the site is easy to use for both visitors and editors:  
       
        The search for a good CMS is over It’s hard to find a system that combines flexibility and scope with simplicity, both in maintainance and development. The search for such a system is difficult. By and large, the open source world offers you the following options:
      In most cases, the more powerful a CMS, the more complex the maintenance and development
      It is usually like that; The functionality of a system also increases the training and operating effort — or the system is easy to use, but is powerless, and must be reporposed for high demands beyond its limits.
      Quite different Processwire : You do not have to learn a new native language, you don’t have to fight plugin hell and mess around with the loop, you don’t have to torment yourself with system-generated front-end code or even learn an entierly new, old PHP framework .
      All our basic requirements are met:
      Custom Content Types Flexible and extensible rights-management Multilanguage Intuitive backend Well curated Plugin Directory Actually working front-end editing Simple templating with 100% frontend freedom In addition, Processwire has an exceptionally friendly and helpful community. As a rule of thumb, questions are answered constructively in a few hours . The development progresses in brisk steps , the code is extremely easy to understand and simple. Processwire has a supremely powerful yet simple API , and for important things there are (not 1000) but certainly one module which at least serves as a good starting point for further development. Last but not least, the documentation is easy to understand, extensive and clever .
      Our experience shows, that you can find a quick and simple solution with Processwire, even for things like extending the rights-management — most of the time a highly complex task with other systems.
      This is also reflected positively in the user interface. The otherwise so “simple” Wordpress crumbles when coping with more complex tasks. It sumbles over its apparent simplicity and suddenly becomes complex:
       
      Old vs. New — Simple and yet complicated vs. easy and hmmm … easy
          Our experience with Processwire as first-timers
      Before we found out about Processwire, we found CraftCMS on our hunt for a better CMS. We were frustrated by the likes of Typo3, WP or Drupal like many here. CraftCMS looked very promising but as we were digging deeper into it, we found it did not met our requirements for some big projects in our pipeline that require many different locations, languages and features. Initially we were sceptical about Processwire because;
      A. CraftCMS Website (and before UiKit also the admin interface) simply locked much nicer and
      B. because it is built on top of a Framework
      It was only later, that we found out, that NOT depending on a Framework is actually a very good thing in Processwire's case. Things tend to get big and cumbersome rather then lean and clean. But now we are convinced, that Processwire is far superior to any of the other CMS right now available in most cases.
      The good
      Processwire is the first CMS since time immemorial that is really fun to use (almost) from start to finish— whether API, documentation, community, modules or backend interface. Every few hours you will be pleasantly surprised and a sense of achievement is never far away. The learning curve is very flat and you’ll find your way quickly arround the system. Even modules can be created quickly without much experience.
      Processwire is not over-engineered and uses no-frills PHP code — and that’s where the power steams from: simplicity = easy to understand = less code = save = easy maintanance = faster development …
      Even complex modules in Processwire usually only consist of a few hundred lines of code — often much less. And if “hooks” cause wordpress-damaged developers a cold shiver, Hooks in Processwire are a powerful tool to expand the core. The main developer Ryan is a child prodigy — active, eloquent and helpful.
      Processwire modules are stable even across major releases as the code base is so clean, simple and small.
      There is a GraphQL Plugin — anyone said Headless-CMS?!
      Image and file handling is a pleasure:
      echo "<img src='{$speaker->image->size(400, 600)->url}' alt='{$speaker->fullname}' />"; I could go on all day …
      The not soooo good
      Separation of Stucture and Data
      The definition of the fields and templates is stored in the database, so the separation between content and system is not guaranteed. This complicates clean development with separate live- and development-environments. However, there is a migration module that looks promising — another module, which is expected to write these configurations into the file system, unfortunately nuked our system. I'm sure there will be (and maybe we will invest) some clever solutions for this in the future. Some inspiration could also be drawn here, one of the greatest Plugins for WP: https://deliciousbrains.com/wp-migrate-db-pro/
      Access rights
      The Access-Rights where missing some critical features: Editors needed to be able to edit pages in all languages on their own location, and content on the rest of the page only in their respective language. We solved it by a custom field adding a relation between a page the user and a role that we dynamically add to the user to escalate access rights;
      /** * Initialize the module. * * ProcessWire calls this when the module is loaded. For 'autoload' modules, this will be called * when ProcessWire's API is ready. As a result, this is a good place to attach hooks. */ public function init() { $this->addHookBefore('ProcessPageEdit::execute', $this, 'addDynPermission'); $this->addHookBefore('ProcessPageAdd::execute', $this, 'addDynPermission'); } public function addDynPermission(HookEvent $event) { $message = false; $page = $event->object->getPage(); $root = $page->rootParent; $user = $this->user; if ($user->template->hasField('dynroles')) { if ($message) { $this->message('User has Dynroles: '.$user->dynroles->each('{name} ')); } // for page add hook… if ($page instanceof NullPage) { // click new and it's get, save it's post… $rootid = wire('input')->get->int('parent_id') ? wire('input')->get->int('parent_id') : wire('input')->post->parent_id; if ($message) { $this->message('Searching Root '.$rootid); } $root = wire('pages')->get($rootid)->rootParent; } elseif ($page->template->hasField('dynroles')) { if ($message) { $this->message('Page "'.$page->name.'" has Dynroles: '.$page->dynroles->each('{name} ')); } foreach ($page->get('dynroles') as $role) { if ($role->id && $user->dynroles->has($role)) { if ($message) { $this->message('Add dynamic role "'.$role->name.'" because of page "'.$page->name.'"'); } $user->addRole($role); } } } if (!($root instanceof NullPage) && $root->template->hasField('dynroles')) { if ($message) { $this->message('Root "'.$root->name.'" has dynamic roles: '.$root->dynroles->each('{name} ')); } foreach ($root->get('dynroles') as $role) { if ($role->id && $user->dynroles->has($role)) { if ($message) { $this->message('Add dynamic role "'.$role->name.'" because of root page "'.$root->name.'"'); } $user->addRole($role); } } } } } With the Droles and Access Groups Modules we were not able to find a solution.
      I thought it was hard to get absolute URLs out of the system — Ha! What a fool I was. So much for the topic of positive surprise. (Maybe you noticed, the point actually belongs to the top.)
      But while we’re at it — that I thought it would not work, was due to a somewhat incomplete documentation in a few instances. Although it is far better than many others, it still lacks useful hints at one point or another. As in the example above, however, the friendly community quickly helps here.
      processwire.com looks a bit old-fashioned and could use some marketing love. You notice the high level to moan with Processwire.
      There is no free Tesla here.
      Conclusion
      Processwire is for anyone who is upset about any Typo3, Wordpress and Drupal lunacy — a fresh breeze of air, clear water, a pure joy.
      It’s great as a CMF and Headless CMS, and we keep asking ourselves — why is it not more widely known?
      If you value simple but clean code, flexibility, stability, speed, fast development times and maximum freedom, you should definitely take a look at it.
      You have to like — or at least not hate PHP — and come to terms with the fact that the system is not over-engineerd to excess. If that’s okay with you, everything is possible — with GraphQL you can even build a completely decoupled frontend.
      We are convinced of the simplicity of Processwire and will implement future sites from now on using it as a foundation.
      Links & resources we found helpful
      API documentation and selectors API cheatsheet pretty handy, not quite complete for version 3.0 Captain Hook Overview of Hooks Weekly.PW newsletter a week, exciting Wireshell command line interface for Processwire Nice article about Processwire Plugins & Techniques that we used
      Custom Frontend Setup with Uikit 3 and SCSS, and Markup Regions Uikit Backend Theme ( github ) Oauth2 login modules In-house development Login with E-Mail Pro Fields for repeater matrix fields (infos, price tables, daily routines) Wire upgrade to update plugins and the core Wire Mail Mandrill to send mails FunctionalFields for translatable front-end texts that are not part of a content type (headings, button labels, etc.) Runtime markup for dynamic backend fields (combination of first and last name) Tracy debugger for fast debugging Textformatter OEmbed to convert Vimeo and Youtube links into embed codes HideUneditablePages thanks to @adrian  
       
    • By John W.
      I'm working on a site where I need to output data for a table. I looked at the Matrix plugin, but, I don't think it does exactly what I want...since my particular table is split into colspans i.e. Direct, Maternal, Carcass, and $Index
      An example of the table output is attached.
      I've pondered using 3 repeaters for the first column titled, EPD, Acc and %Rank.  Each one of these repeaters would have the fields for CE, BW, WW, YW, MCE....
      The last thing I want is to have to create a very long list of inputs vertically down the page for each field in the back-end for my client.
      Any PW gurus here, maybe help me out? If there is absolutely, no alternative to make input simple for my client, let me know if I have to buy ProFields.
      thanks mucho!